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....
- Select an option with an additional template and get it filled on the owner.
- Drop support for onchange, too many bugs to workaround.
- Improve demo data.
- Improve tests.
- Almost cool material icon, this is an app now!
- Fun pics.
# Conflicts:
# base_custom_info/__manifest__.py
* 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.
# Conflicts:
# base_custom_info/__manifest__.py
# base_custom_info/i18n/es.po
OCA-git-bot
Laurent Mignon (ACSONE)
oca-travis
Fanha Giang
Jairo Llopis
Sergio Teruel Albert
Pedro M. Baeza
OCA Transbot
Stéphane Bidoul (ACSONE)
Carlos Incaser