How to avoid problems with access rights or user groups when updating an app or module?

Question

Basically, we are all aware that the views are restored and that is why we always customize them through inheritance (Studio or development).
But it appears that other things such as "user groups, access rights, etc." (copy/paste from the Support Team, the "etc." should be clarified) are restored too. We noticed it could affect the financial reports too and probably other standard records coming with the app/module.

For example, if you simply rename a user group, a manual (sometimes asked by th

Chloé Vandenhove (cvh) · Accepted Answer

The only way to avoid this is to set "No update = true" using the "button" (yes, it is a button) in the "View Metadata" after editing a standard record* :  https://drive.google.com/file/ [1] d/1AdD0ylYN9H4dDMbjx8MVEiTveU- eh6DK/view
The consequences are the following :
- If you can avoid such a customisation, avoid it :-)
- If not, make sure the records you edit cannot be updated
- If you already performed such a customization (for Studio Approvals for example), check them with the aim to antici

Publicaciones relacionadas	Respuestas	Vistas
Link attachments with wanted record and model Resuelto quickstart	1 abr 25	6627
✅Change the Account on Payments in Odoo quickstart	0 mar 25	973
✅Change the Account on Payments in Odoo quickstart	1 mar 25	30
✅ Change the order date to the Old date quickstart	0 mar 25	824
Plugin ALMA quickstart	3 sept 24	3997

Se marcó esta pregunta

¿Le interesa esta conversación? ¡Participe en ella!