FrancoisGe
fd98a3f4a0
This commit allows the correct activeFields to be used depending on the view used to open an x2many field. Before this commit, if we had an x2many field with a list view and a form inline view with the same field containing a different context depending on the view. The context of the form view will always be used. This is a problem: If we have an inline form view with fields common to the list view, the context of the activeFields in the form view will always be used and we will try to combine the different modifiers (required, readonly, etc.). We don't want to do this, we want to use the activeFields of the list view when we open the record in the list and the activeFields of the form view when we open the record in the form view. Solution: When we create the activeFields, we'll use the activeFields from the list view and complete them with those from the form view. We will therefore no longer replace or merge them. Then, when we open a record in form view, we'll use the activeFields from the form view and when the form view closes, we'll restore the activeFields from the list view. closes odoo/odoo#129989 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials