[trunk/7.0]Lines Journal Entries
Bug #1233900 reported by
Luis Torres - http://www.vauxoo.com
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Low
|
OpenERP Publisher's Warranty Team | ||
Bug Description
1) Steps to reproduce the issue you have observed
1.- Create a new journal entry
2.- Select a journal
3.- Add a new line, and select an account of partner, with an amount in debit
4.- Create a new line, with values by default, not be change nothing
Can find a demonstrative video here: https:/
2) The result you observed
I observed that the new line was removed when you selected save register
3) The result you expected
I expect that the line not was remove
| Changed in openobject-addons: | |
| assignee: | nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| summary: |
- Lines Journal Entries + [trunk/7.0]Lines Journal Entries |
| Changed in openobject-addons: | |
| assignee: | OpenERP R&D Addons Team 3 (openerp-dev-addons3) → OpenERP Publisher's Warranty Team (openerp-opw) |
| tags: | added: maintenance |
Revision history for this message
| Mohammed Shekha(Open ERP) (msh-openerp) wrote | #1 |
To post a comment you must log in.
Hello Luis Torres,
I went through your query but this does not seems a bug at all, instead a behavior, no doubt there are all necessary fields filled by default_get but still you did not changed any thing on that record explicitly, so one2many line still not get dirty(no change through UI) so while saving web-client consideres only dirty/changed elemets and hence this line is ignored.
The fields always get dirty when you explicitly change it from UI so this is desired behavior according editable one2many API, you can even see in your video when you explicitly change name in line record got saved.
If you want something like when you come to next line and want to save that record with default values as it is then I would suggest either go through that line using TAB key or just press enter then save the whole record.
According to your bug post it is concluded that you want to save that record which has all required value which is filled by default_get then I would say it will create unnecessary records for which user still not give confirmation(RETURN KEY or Change in line), if you press enter or change something in line or you go through whole record using TAB key then it is considered that you really intended to save that record.
If user did not confirm to save that record then we ignore that record, if we save unintetional records then user have to explicitly delete that record.
Hope this will clears your doubt on editable list view.