odoo/odoo#200918
Created by fw-bot
Merged
at 3c95a45041ebe03604b263acd3ad29f106495c24
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:master-18.0-opw-4594796-huvw-421478-fw
- head
- e3e58d719582a108d49c367f193dd786ca278666
- merged
- 8 months ago by Bugfix, Hubert Van De Walle
| odoo/odoo | |
|---|---|
| 18.0 | #200197 |
| saas-18.1 | #200823 |
| saas-18.2 | #200896 |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #200918 |
[FW][FIX] base: add properties definition field automatically in views
Steps to reproduce
- Install repair,web_studio
- Go to repair
- Open any record
- Open studio
- Switch to the misceallaneous tab
- Click on the Operation Type field
- Add the "Technical / Receive notifications in Odoo" group in "Allow visibility to groups"
TypeError: Cannot read properties of undefined (reading '0')
at PropertiesField._getSeparatorFoldKey
Cause of the issue
Since the user doesn't have that group, the field picking_type_id will no be available.
repair_properties = fields.Properties(
'Properties',
definition='picking_type_id.repair_properties_definition'
)
That field is needed as it's the definition field for the repair_properties field.
Solution
When postprocessing views, we already add some fields that are needed by others. We can do the same for properties fields.
Forward-Port-Of: #200197