Hi my Friend
From what I’ve seen, this usually isn’t a checkbox issue its almost always related to permissions or UI logic.
The first thing I would check is field-level ACLs on the checkbox field. If another user doesn’t have read access to that field, the value won’t display for them, even though it’s saved. I’ve run into this a few times where the field looks unchecked simply because the user can’t read it.
Next, I’d look for any UI Policies or Client Scripts tied to the incident form. Sometimes these are role-based and can hide the field, make it read-only, or even reset the value when the record is loaded for certain users.
I’d also double-check the dictionary settings to make sure the field is actually stored on the table and not behaving like a derived or display-only field.
Another thing worth checking is form personalization. Different users may have personalized their form layouts, and the field could be hidden or overridden for them.
Finally, I’d confirm the value is really being saved by checking the record directly (for example in the database or via a background script). If the value is true there but not visible on the form, that pretty much confirms it’s an ACL or UI logic issue.
In my experience, when one user can set the checkbox and another can’t see it, the fix almost always ends up being field-level read access or a UI policy/client script condition.
@Sshova - Please Mark as Accepted Solution and Thumbs Up if you found Helpful!!
