May I add my opinion. Logical rationale: If you allow a situation as shown on screenshot in #16, then #17 should not happen. That is: a change of a *line* should be limited to that line, including changing the date. So, if different dates for each line are allowed in the first place, you should just keep those dates (= leave them untouched) not affected upon changing one of those lines. In light of this the "bug" seems to be more an annoying inconsistency, if I understand correctly.
Accounting rationale: Well, IMHO this *is* a basic accounting question. Similar to "hierarchies" quite well and consistently implemented in OpenERP (structure throughout accounting, products etc.), this should be applied to journal entries. Why would you want a "centralised" journal (higher hierarchy so to speak) if the entry lines (lower hierarchy) within would not be allowed to differ (including the dates)? While this seems to be the case, it is currently quite annoying when you simply want to correct one line out of a 100, and suddenly all dates are synchronised involuntarily. Legal rationale: There is no place worldwide I could think of where either solution would pose a problem. Software design: Assuming good practice, -- leave the choice to the user (e. g. accountant) if no other good reason precludes that choice; -- give freedom of choice/change on lower hierarchical levels, that's what they are for. In our example, someone who does not want different dates per line will just keep them alike, and vice versa. But again, in unchanged 5.0.12 it's currently simply a question of inconsistency occurring only when making changes within a "centralised" journal, IMO. A more advanced approach would allow to set your favoured approach in the journal settings: e. g. if you choose "centralisation" you might tick a checkbox "synchronise all dates per period", or similar ... Best regards, -- Effective Date of Move and Movelines has to be the same? 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: Opinion Status in OpenObject Addons 5.0 series: Fix Released 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 _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-accounting Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-accounting More help : https://help.launchpad.net/ListHelp
