Conversation
|
@namtnt could you please squash the commits? And the FIX/IMP commit msg should not has version prefix, so that we can pw-port down-port it w/o the need to update commit msg. |
| user_role_ids = fields.One2many( | ||
| comodel_name="res.users.role", | ||
| string="User Roles", | ||
| string="Roles", |
There was a problem hiding this comment.
I don't think we need to change this. Do you have a good reason for this?
There was a problem hiding this comment.
We need this change to fix this warning WARNING odoo odoo.addons.base.models.ir_model: Two fields (user_role_ids, role_ids) of res.users() have the same label: User Roles. [Modules: base_user_role and mail]
namtnt
changed the title
…though the user has roles in form view
namtnt
force-pushed
the
19.0-fix_base_user_role
branch
from
b75e07b to
2a4cfeb
Compare
| user.show_alert = user.role_line_ids.filtered(lambda rec: rec.is_enabled) | ||
|
|
||
| role_ids = fields.One2many( | ||
| user_role_ids = fields.One2many( |
There was a problem hiding this comment.
No, because the field is a computed non-store field
|
This PR has the |
5 participants
Summary
Currently, native Odoo already defines a
role_idsfield (m2m). This overrides therole_idsfield (o2m) from thebase_user_rolemodule, which causes the User Roles field to be empty in the User list view.Changes
Renamed
role_idsfield touser_role_ids.Reproduce:
Create a User and set a role for the User
Back to User list view -> User Roles is empty
