
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 12:38 PM
Hello everyone,
The state field in the incident form is being changed incorrectly. Instead of going to one of the options, such as "new", "in progress", "pending", it is changing it to a non-existent value, such as "4". I want to know what is broken about this because there is no state in the incident configured with the value 4. Is there a way to find out what changed the field value within the platform?
Regards,
Leandro Oliveira
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 12:49 PM
First step would be to try using the field watcher as you progress through an incident - this can help you identify what actually changed the value.
https://docs.servicenow.com/en-US/bundle/utah-api-reference/page/script/debugging/concept/c_FieldWat...
On a side note, normally the actual values for states are actually numeric - you might find somewhere that a script is passing in "4" instead of 4, which is being treated as a string vs. numeric value match.
Michael D. Jones
Proud member of the GlideFast Consulting Team!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 12:49 PM
First step would be to try using the field watcher as you progress through an incident - this can help you identify what actually changed the value.
https://docs.servicenow.com/en-US/bundle/utah-api-reference/page/script/debugging/concept/c_FieldWat...
On a side note, normally the actual values for states are actually numeric - you might find somewhere that a script is passing in "4" instead of 4, which is being treated as a string vs. numeric value match.
Michael D. Jones
Proud member of the GlideFast Consulting Team!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2023 12:59 PM - edited 11-02-2023 01:00 PM
Thanks @Michael Jones - !
Your solution solved my problem. It was a script that was setting this value.
Regards,
Leandro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2025 07:06 PM
Hi @Michael Jones -
Field watcher is not supported in Xanadu, do we have any alternative to track field value changes now