summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_model.js
diff options
context:
space:
mode:
authorNicolas Martinelli <nim@odoo.com>2017-10-11 14:59:52 +0200
committerNicolas Martinelli <nim@odoo.com>2017-10-12 13:02:33 +0200
commit179de9b55f4d3e6006cdbfaa77f67ef4956d0628 (patch)
tree6bfef877b00f23eede676044e0274e9c3fe666d6 /addons/web/static/src/js/views/basic/basic_model.js
parentdf124080b624a8bdb86fec352fe690725ed36bac (diff)
[FIX] sale: layout sequence
- Create 2 companies A & B (not linked) - Create a user Demo allowed in both companies - Create a Sale Layout Category ('TEST') - In company A, create a SO and add 'TEST' to the line - Switch to company B, create a SO and add 'TEST' to the line - In the Sale Layout Category, change the sequence of 'TEST' An access error appears. On a SO, `layout_category_sequence` is a stored related. It means that when we change the sequence of the layout, all SO are updated, including the SO to which we don't have access (in this case, the SO of company A, since our user has switched to company B). While it seems that `layout_category_sequence` was intended to be used in order to keep the historic value of the sequence, this is not the actual behavior. Indeed, the method `order_lines_layouted` uses the SO lines in their original order, which doesn't use `layout_category_sequence`. In summary, this related field causing an access error is never used. opw-774787
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_model.js')
0 files changed, 0 insertions, 0 deletions