Take a look at the records in a list or form view and make sure they are what you think they are. Validate assumptionsīefore starting down the path of more complex debugging techniques, check the basics. So, what should we do next? With practice, you’ll start to get a better feel for when you should try one thing or another, but here’s the approach I generally take. However, when the results come back from the API call, we notice that there are missing records in the response and we can’t see every field that we expect. We want to retrieve a list of Incident records using the Table API. Let’s start by looking at a common scenario we might encounter. Handling Unexpected Results When Retrieving Records I’m going to introduce a few concepts that are not well known later in this post: The Log File Tailer and the X-WantDebugMessages & X-WantSessionNotificationMessages headers. In this post, we’ll explore some of the options available for debugging inbound REST API calls and the Business Rules / ACLs that might be impacting those calls. Have you ever run into unexpected behavior when making inbound REST calls to your ServiceNow instance? Perhaps the result of a GET doesn’t contain all of the records you expect it to, or nothing happens when you try to modify a record.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |