
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 09:31 AM
I have a custom field on sys_user table to check a box to denote if the contact is a VIP. This displays on the customer_contact form:
Dictionary Info: customer_contact.vip
Table: sys_user
Field: vip
When I check the vip box on the customer_contact form then save the form, the box gets cleared, won't accept my change. If I change the view from "Case" to "Default view" it does allow me to change the field and save it. Why does this happen? Ideally I want to grant certain users the ability to set the VIP field but those users get this behaviour and they are unable to use the Default view unlike I can as the admin with full access to the user table.
Any thoughts?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 11:19 AM
I've seen something like this happen when they are 2 of the same fields on a form. For example, you could be having one VIP field on the Customer Contact form and the same one present under one of the form sections.
In such cases, the click action occurs on only one field... and the other (hidden) field still remains unchecked, which upon saving, still reflects false.
I presume you have this scenario.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2024 03:30 AM
Much obliged @AnirudhKumar it was indeed due to the field being duplicated in more than 1 section. Because the contact table is extended from user (plus we have a domain separated instance) it wasn't too obvious but after some digging I found it. Thanks for the help.
Paul

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 11:19 AM
I've seen something like this happen when they are 2 of the same fields on a form. For example, you could be having one VIP field on the Customer Contact form and the same one present under one of the form sections.
In such cases, the click action occurs on only one field... and the other (hidden) field still remains unchecked, which upon saving, still reflects false.
I presume you have this scenario.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2024 03:30 AM
Much obliged @AnirudhKumar it was indeed due to the field being duplicated in more than 1 section. Because the contact table is extended from user (plus we have a domain separated instance) it wasn't too obvious but after some digging I found it. Thanks for the help.
Paul