- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2021 08:44 AM
Hi
Was trying to create incident in ServiceNow via the below API curl call but the incident description field is not updated for regular users, it works for admin though! There was an access control (ACL) for description which I deleted but still the description field is blank when incident is created.
Curl Call -
curl --location --request POST 'https://dev80009.service-now.com/api/now/table/incident' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic dGVzdDp0ZXN0' \
--header 'Cookie: BIGipServerpool_dev80009=2609075978.55360.0000; JSESSIONID=03AB5C528F99C3FE4CA1954E3EAA8747; glide_user_activity=U0N2MzpVb1RSTjJDSG9ZOEJTQnR2eWFIQ0tqNmRROFZCcVQzTTpPRWpoYm1jZVBML28vWktCT0E5Y2VYclNac0pldXpsQmpINlBLV251ZktrPQ==; glide_user_route=glide.e0bd65849cb91a6b8a16a2533b5fca6d' \
--data-raw '{"short_description":"short test","description":"test"}'
Can someone suggest what should be done here?
ACL which was deleted -
NO ACL for description -
Postman result with description blank -
Solved! Go to Solution.
- Labels:
-
Integrations

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2021 09:17 AM
Hi,
Create a new ACL on incident description field as below and your issue will be resolved.
This will allow your service account to update the incident description without any role restriction.
Now, talking about the situation where OOB ACL (which you deleted) is existing.
In that case you could have done by creating another write ACL on Incident Description field with condition as below:
Kindly mark my answer as Correct and Helpful based on the Impact.
Regards,
Alok
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-24-2021 12:16 AM
Thanks Allen for the help! Marked this helpful!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-24-2021 07:13 AM
Hi,
Alright, that's fine.
Just to reiterate again, I covered creating the ACL in my post above, but also wanted to explain why you'd have to.
Thanks and take care!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2021 08:58 AM
Hi SP,
Did you checked with static value?
Is your Description have special characters?
Have you tried it with REST API Explorer?
Thank you
Prasad

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-18-2021 09:17 AM
Hi,
Create a new ACL on incident description field as below and your issue will be resolved.
This will allow your service account to update the incident description without any role restriction.
Now, talking about the situation where OOB ACL (which you deleted) is existing.
In that case you could have done by creating another write ACL on Incident Description field with condition as below:
Kindly mark my answer as Correct and Helpful based on the Impact.
Regards,
Alok

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2021 10:18 AM
Hi,
Hope you are doing well!
Just following up, did my response or the other response answered your query then please do mark the appropriate answer as Correct and close this thread.
Regards,
Alok