Incident Closure via REST API Fails with "Cause code" Mandatory Data Policy Exception
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi Team,
We are facing an issue while resolving Incidents through the ServiceNow Table API.
When updating an Incident to the Resolved state via a REST API PUT request,
we receive the following error:
Observations:
- The Cause Code field is being passed in the API payload.
- The Incident can be resolved successfully from the UI.
- The issue occu
- rs only when resolving through the REST API.
- A Data Policy is enforcing Cause Code as mandatory.
how to fix it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Validate that the cause code you are sending is correct. From the looks of it, it's a custom field, so not sure if it's a string or a choice field. If it's a choice field, make sure it's the correct VALUE of the choice (not the LABEL).
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
As mentioned by Mark, please validate the choice value in the payload you are sending
Please let us know if that resolves the issue
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi Ankur,
Yes, u_cause_code is a choice field, and we are passing a valid value in the API payload. However, the value is not being updated in ServiceNow, and we continue to receive a Data Policy Exception stating that Cause Code is mandatory. how to fit it
