[tryton-dev] reconciliation in GeneralLedgerLine

2017-03-29 Thread Richard PALO

I prototyped adding display of line.reconciliation.name in General Ledger
reports iff the reconciliation date is '<=' to the end_date of the end_period
(if specified) or of the fiscal year.

This seems to work nicely in the generated report, but for 'correctness' I'd
like to filter the column already in the GeneralLedgerLine output screen 
instead.

I initially thought to put the fields.Many2One for account.move.reconciliation I
added in a fields.Function  and provide a 'getter' function get_reconciliation,
but then I realised that I probably didn't have the context necessary (namely
GeneralLedgerAccountContext) in order to do pick up fiscalyear and end_period.

How could this be done? Is there any way to filter columns as opposed to 
records?

cheers,
--
Richard PALO

--
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/05d06957-fc0c-3059-68f0-841198ff6a47%40netbsd.org.


Re: [tryton-dev] Removal of Property

2017-03-29 Thread Cédric Krier
On 2017-03-29 16:13, Sergi Almacellas Abellana wrote:
> El 29/03/17 a les 00:12, Cédric Krier ha escrit:
> > I would like to commit it ASAP to get enough time to find all bugs
> > before the release.
> 
> Indeed bugs can be found before commiting. It's a mather of appling all of
> the reviews. I have some script in order to update them when applied that I
> attach in this mail if is usefull for somebody else.
> 
> I've found the following:
> 
> - Creating a party with no stock locations clears the customer_location and
> supplier_location values of all the parties. Indeed, setting the the
> location value of a party to any values sets this value for all of the
> parties. I've reproduced it on a migrated database but I haven't tested on a
> new database.
> 
> I've tested on this specify model, but I'm wondering if the other models are
> also affected.

It should be fixed in last patch set. Indeed this MultiValue model was
missing the One2Many so it was using all records.

> > It will be good also to have some migration test.
> 
> After the migration I get a lot of this warnings like this:
> 
> WARNING trytond.convert Could not delete id 20 of model ir.property because
> model no longer exists.
> 
> Is this the expected behaviour?

Yes, the system does not know any more about ir.property

> This warning are also shown when updating the database for second time.
> The only way to remove this warnings was executing this query on the
> database:
> 
> delete from ir_model_data where model = 'ir.property';
> 
> Should we add this to the migration page?

Yes it could even if leaving them does not hurt at all but it is only
after the migration was succeeded.

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

-- 
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/20170329151608.GN6408%40tetsuo.


Re: [tryton-dev] Removal of Property

2017-03-29 Thread Sergi Almacellas Abellana

El 29/03/17 a les 00:12, Cédric Krier ha escrit:

Hi,

The patches that removes the Property fields is ready for testing. It
is passing all the tests.

https://bugs.tryton.org/issue2349


First of all: Thanks for the big work :)


I would like to commit it ASAP to get enough time to find all bugs
before the release.


Indeed bugs can be found before commiting. It's a mather of appling all 
of the reviews. I have some script in order to update them when applied 
that I attach in this mail if is usefull for somebody else.


I've found the following:

- Creating a party with no stock locations clears the customer_location 
and supplier_location values of all the parties. Indeed, setting the the 
location value of a party to any values sets this value for all of the 
parties. I've reproduced it on a migrated database but I haven't tested 
on a new database.


I've tested on this specify model, but I'm wondering if the other models 
are also affected.



It will be good also to have some migration test.


After the migration I get a lot of this warnings like this:

WARNING trytond.convert Could not delete id 20 of model ir.property 
because model no longer exists.


Is this the expected behaviour?

This warning are also shown when updating the database for second time.
The only way to remove this warnings was executing this query on the 
database:


delete from ir_model_data where model = 'ir.property';

Should we add this to the migration page?




--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk

--
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/027ff2b0-d07a-98fa-cb87-d99128d5d61c%40koolpi.com.


update_modules_review.sh
Description: application/shellscript