What sets this field readonly?

[ericgilmore]

ver. Tokyo

I have an instance where Incident.Number is set to readonly all the time. Upon taking a look at the field I noticed that there exists an ACL on incident.number for write. It's configured to require the role snc_internal and to allow write if the Incident is not resolved or closed.

Ok, so as an admin, I watch the number field and reload the form. The first entry that pops up in the references an ACL. The odd thing is, it's NOT the incident.number/write ACL. It's says...

But, there is NO incident.number/read ACL.
Also, I've checked Business Rules, UI Policies, Client Scripts, the Dictionary Entry, and Data Policies.

I can not pinpoint where this field is set ReadOnly.

Are the entries seen in the watch log correct? Maybe I've never paid close attention to the ACL entries in the watch log to notice that this may be normal. 

Is there somewhere else I can look?

[SanjivMeher]

I think there will be an ACL on task.number which is inherited to the child tables such as incident,change_requests etc.

I would also suggest looking at the dictionary record of the number field.

There could be list of ACLs and also dictionary override. There are few dictionary override for which read-only is set to true 

[Aman Kumar S · Accepted solution]

Hi @ericgilmore 

I believe its still pointing to the record ACL and not the field ACL, You can also click on "i" icon and the "+" sign to get further details.

As far as the configuration goes, you can find the details in this ACL:

This ACL is inherited at child level which is Task -> Incident

[ericgilmore]

Yes it was a Dictionary Override. In the related list of dictionary overrides there is an entry for incident. Upon examination, this override is in fact set as readonly. 🙂

I just missed it on the first pass through.

[SanjivMeher]

@ericgilmore Looks like you marked the wrong response as Correct Answer.