When changing the custom info template, some recomputation triggers are launched
that can involve records that the user changing the template has not access to
(for example, a record of other company).
Putting this, we avoid the problem.
- Put force_save=1 for allowing the web client to send readonly values to server
- Switch widget="selection" to "many2one" default with options because it's not
supported anymore in tree view
- Move value_id to parent view.
We must avoid to rely on the order in which computed fields (including related fields) and constrains methods are applied.
Due to a recent change into the ORM, the contrains on the model_id into CustomInfoTemplate is now called AFTER the recompute of the related model field into property_ids.info_value_ids
As side effect, when the constrains is called, the model on the info value is already updated with the new value and we no more know the old value....
* Now you can define properties types, and access rules are inherited from the model/record
linked to the custom info record.
* Simplified version of computed value.
* Implement for res.partner.
* Add tests and fix bugs discovered in the meantime.
* Allow to disable partner custom info tab, and custom info menu.
* All of it can be set within general settings.
* Now, by default, this module does not display custom info for partners unless in demo mode.
Better fit for a base module.
* You can disable the top menu entry too if it disturbs you, or enable it for everybody.
* Give a special form when editing in partner custom info tab.
* Sortable properties.
* Sort values at onchange time.
* Improve performance in onchange.
* Split in several model files.
Pedro Castro Silva
OCA Transbot
OCA-git-bot
oca-travis
Enric Tobella
Pedro M. Baeza
Adrià Gil Sorribes
Alexandre Díaz
Laurent Mignon (ACSONE)
Fanha Giang
Jairo Llopis
Sergio Teruel Albert
Pedro M. Baeza
Stéphane Bidoul (ACSONE)
Carlos Incaser