Entries encoding by move dont save correct date
Bug #398805 reported by
Eduardo Ruiz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Invalid
|
Undecided
|
gpa(OpenERP) |
Bug Description
linux - Version 5.0 & trunk
Entries encoding by move dont save correct date you are seen in the view.
When creating new record, it proposes today's value buy when you save it changes to first day of the mounth.
You can edit and save the correct value you want. In next move, it saves the previous date you saved even though you typed a different one.
Related branches
Changed in openobject-addons: | |
status: | New → Confirmed |
Changed in openobject-addons: | |
assignee: | nobody → gpa(tiny) (gpa-openerp) |
status: | Confirmed → In Progress |
To post a comment you must log in.
Hello Eduardo,
Its the obvious behavior.
Moves exist due to Move Lines only.
The date on Move shows the recent activity on that move.
The Date on Move is based on this Logical scenario:
1. When you Create a move, you have the current date as default.you can save any date at this point of time.
2. You go to create a move line corresponding to that move, There is no EFFECTIVE DATE field on move line form view dialog.So, current date will be saved as effective date for move line, and so this date appears on move. so you have 1 entry of move line.
3. You go to Entries Encoding by Line,select the journal and period, you will see the concerned entry,edit its date,this date which shows RECENT activity,appears on move date too.
So, One useability improvemnt can be as showing effective date on Move Line form view dialog from account move.
I hope this has made your doubt clear.
Thank You.