ServiceNow TableAPI integration should support filters/queries
E
Elliott Spira
The ServiceNow TableAPI integration is great, I can fetch from all sorts of standard and custom tables.
The issue is that many of the tables I want often have 10's of thousands of entries and as the integration works slowly through many entities, are unlikely to ever complete a sync.
One key example is
cmdb_ci_rel
which contains key relationships between entities.If the integration could expose some of the filters from the table API through the mapping configuration, that would be incredibly enabling!
G
Glenn Moen
We are facing a similar situation with the sys_user_group. Our org has 20k groups, but I am only interested in groups of a certain type. It reduced the number of groups down to 200.
We would also like to see the inclusion of additional query parameters. These include name-value pairs(a different way to filter), sysparm_display_value(key, display values, or both), sysparm_exclude_reference_link(easier to use id fields), and sysparm_fields(control fields returned and can be used to auto join).
There are a few other parameter that could also be helpful on a more limited bases. Here is a link to documentation on the Table API. https://www.servicenow.com/docs/bundle/washingtondc-api-reference/page/integrate/inbound-rest/concept/c_TableAPI.html
The lack of api level filtering is also causing issues with entity deletion during resync. Because the resync compare uses the api results directly(containing all results), our jq query filter for incident state doesn't cause closed incident to be removed from Port.
Matan Grady
Glenn Moen: Thank you for all this additional context and feedback. Your point is definitely clear. I also added you as a voter for this request.