Number field is now readonly, how, when?

[ericgilmore]

ver. Tokyo
Scenario: An instance, with writable Number (Task.Number) field on Case, Change Request, and Incident

So this instance I've been tending had a writable Number field on (Case, Change, and Incident). Well, one day this changed, and now the field is readonly.

So I wanted to know; 1) When this changed, 2) Who changed it and, 3) What the new config was.

I've checked:
 - ACL's > I see no newly defined or changed WRITE ACL's for any of these tables
 - Task table > No changes
 - Client Scripts > I see nothing related to these tables and the Number field
 - Business Rules > Again, nothing explicitly linked to the Number field or readonly attributes.
 - Dictionary Overrides > I did see something for Incident here, but it wasn't triggered unless certain states were set.

 - Debug session > I did see a READ ACL referenced in a session, but that's READ not WRITE

I have NOT explicitly reviewed all Script Includes, but that's not the usual way to set a field to readonly.

Is there somewhere else I should search for this configuration?
 

[Sandeep Rajput · Accepted solution]

@ericgilmore Please check if there is any data policy defined on the number field. Also, check if there is any dictionary override on task table which is making the field read only.

[ericgilmore]

It was a Dictionary Override that I missed. Once I found it, and confirmed that was the explicit reason readonly had changed, I was good to go.

Thank you for all your help!

[Vishal Birajdar]

Hi @ericgilmore 

Is ACL returning to false or true....??

Below article might help you....!!

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0783470