summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/fields/field_utils.js
diff options
context:
space:
mode:
authorAaron Bohy <aab@odoo.com>2017-06-26 08:42:08 +0200
committerAaron Bohy <aab@odoo.com>2017-06-27 14:12:31 +0200
commit816a3cd2c1edeff2ffa2e90c0f8a25795804f84d (patch)
tree26503a6eb7f268fea401d1254be909510efd3f08 /addons/web/static/src/js/fields/field_utils.js
parent4881f942cb7cad51b8472425830c8444cfe09d1a (diff)
[FIX] web: ViewManager: filter out some keys from context
A traceback occured when trying to create a BOM by going to Inventory > Master Data > Products, on a product form view clicking on the BOM stat button, and then on 'Create'. This was a context problem: the context of the 'Products' action was passed to the 'BOM' action without removing action specific keys like 'default_*' or 'search_default_*'. For instance, it contained a 'default_type' key, and as type is also a field of the mrp.bom model, the python tried to interpret it, except that the given value wasn't a correct value for mrp.bom. When a button is clicked, we mix contexts coming from different places to execute the new action. For some of them, we already filtered out those action specific keys. This fix is simply to make the piece of context adding the problematic keys pass though the filter as well.
Diffstat (limited to 'addons/web/static/src/js/fields/field_utils.js')
0 files changed, 0 insertions, 0 deletions