Servicenow-missing records issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
By using ServiceNow Table API to pull data from ServiceNow There appear to be record differentials between data pulls that are not explained by new records coming in or existing ones being updated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @sivakoteswaV ,
can you provide more details about your question?
Thank you,
Hemanth
Certified Technical Architect (CTA), ServiceNow MVP 2024, 2025,2026
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hello @sivakoteswaV
Are you saying that when you pull data from ServiceNow using the Table API, the records returned from one extract don't match the records returned from another extract, and the differences cannot be explained by normal activity such as new records being created or existing records being updated.
Like at 9 am Today you called Incident Table API and count is 100 incidents and then at 10 am same Incident Table API being called gave you incorrect count like maybe 80.
If the above analysis is incorrect, then could you please elaborate your requirement and if the above analysis is correct, then need to learn more about how you are calling Table API and whether it used to work or a new implementation where ACL/role/sysparm_limit or sysparm_offset could be causing this mismatch.
Hope that helps!
