- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2022 12:15 PM
Hi,
With our connector to ServiceNow, our clients are wondering why when they run a sync job from our platform to update fields in a ServiceNOW table, that nothing is updated in rare situations.
We receive a status of 200 from you, and the reason the field updates are not occurring is due to these particular fields in the ServiceNOW table being read-only. Is this expected behavior, and is there a solution for this beyond our clients having to create ACLs?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2022 12:37 PM
Right. If a field is marked as readonly via ACL or at dictionary level, it can't be updated. If it is just at UI policy level, it can be updated via API.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2022 12:30 PM
You need to make that field editable for the clients so that they can update it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2022 12:33 PM
Well, these are fields in their own ServiceNow orgs. So what you're saying is that there's no way for an API connection to update a read-only field's value on a table in ServiceNOW? Is that correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2022 12:37 PM
Right. If a field is marked as readonly via ACL or at dictionary level, it can't be updated. If it is just at UI policy level, it can be updated via API.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2022 12:39 PM
Got it. Thank you very much for clarifying @SanjivMeher