When using userprefence sentry rules to block access to more fieldsyou get an sentry exception when trying to save the entity
Status: Not prioritized
Description
When using userprefence sentry rules to block access to more fields you get an sentry exception when trying to save the entity, example::
Example:
prefsection: Rights-person-Existing
prefkey: udpersonsmall.double05
level: 4
owner_id: usergroup id
value: 0, No access
This works, it hides the field in CRM, but when a value is set in the field, the following error occurs on save:
(which actually hides the sentry error)
If you do the same on contact level, you get the following error:
When the field is empty no error occurs.
Seems like the system is trying to save an field it does not have access to. Is there any other standard way to hide more fields for some usergroups, and make them editable for others?
Tested with the following field types: long, double, string
Tested on the following entity's: contact person
Versions tested: 8.5 R15, 9.1 SOD
Details
| Issue id | 9933 |
| Registered | 25 Jun 2020 |
| Last modified | 2 Jan 2025 |
| Severity | High |
| Area | Sales |
| Status | Not prioritized |
| Target release | |
| Type | Bug |
Comments
2025.01.02]
Thank you for taking the time to report the issue. After careful consideration, we have decided not to address this bug at this time. Our decision is based on one or more of the following reasons:
We appreciate your understanding and hope you can agree on this. This allows us to focus on delivering greater value in other important areas.
[2020.10.27: a]
We created an workaround for this bug for our customer (field type int): in the webscript BeforeSaveContactEntity we set the value of the locked field to the database value (from UI comes Value=0), then the sentry check is not active.