openerp-expert-accounting team mailing list archive

["Jay \(Open ERP\)" <jvo@xxxxxxxxxxx>]

Hello Invitu,

We had a discussion with some experts and it is widely accepted that the
effective date of move line should always reflect the effective date of
move.

So, to maintain the consistency, the field is set to be
related(functionally, the effective date of move should impact on the
effective date of its move lines).

Hope this is clear.

Thanks.

** Changed in: openobject-addons
       Status: Confirmed => Invalid

** Also affects: openobject-addons/5.0
   Importance: Undecided
       Status: New

** Changed in: openobject-addons/5.0
       Status: New => Confirmed

-- 
The Centralisation check is required at write(), Date of move and effective date of move line do not behave as expected on write()
https://bugs.launchpad.net/bugs/519133
You received this bug notification because you are a member of OpenERP
Accounting Experts, which is a direct subscriber.

Status in OpenObject Addons Modules: Invalid
Status in OpenObject Addons 5.0 series: Confirmed

Bug description:
Hello

When modifying an entry line in a centralized journal (journal.centralisation=true), all the entry line dates get modified and take the modified entry line value.

The entry line dates should not be changed

I guess the solution is in the write function in account_move_line.py where we should find some 'if journal.centralisation:...' as it is in the create function.

Regards