Getting {"result":{"code":400,"error":"Attribute: '' is missing in payload."}} in Outbound REST call
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2024 02:46 AM
Hi Team,
I am working on to send outbound message to Servicenow instance through REST API. Configured below Outbound api and business rule , and getting error: {"result":{"code":400,"error":"Attribute: 'sys_class_name' is missing in payload."}}
Outbound:
Business rule:
No clue still getting error:
Please help to overcome issue.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2024 02:57 AM
Hi @maneesh3 ,
Can you also pass the classname dynamically as current.sys_class_name.
Incident is in Global and Rest Message is in Customer service.
May be any cross scope issues.
If the above information helps you, Kindly mark it as Helpful and Accept the solution.
Regards,
Najmuddin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2024 03:31 AM - edited 12-02-2024 03:40 AM
Hi Najmuddin,
Thanks for reply. but still getting same error after updating BR to dynamic for sys_class_Name:
Output:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2024 04:22 AM
Hi @maneesh3 ,
Share the request body screenshot. Remove the line number 11 from your script and then try.
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay
-------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2024 04:57 AM
Hi Runjay,
Removed line 11 in BR and still receiving error: