Table API vs. Import Set API – Best Practice for Trusted Identity Data Integration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 11:17 AM
We are currently integrating our Oracle Identity tool with ServiceNow to manage user provisioning. Here’s our setup:
We are using the Oracle out-of-the-box (OOTB) connector to create and update user records in the sys_user table.
User attributes such as job code, department, and other metadata determine group memberships. The connector handles this by adding users to the sys_user_grmember table.
The data coming from Oracle Identity is trusted, clean, transformed, and validated. This same data is used to provision other systems like ERP, EPIC, Active Directory, UKG, etc.
The connector performs lookups on core tables (cmn_location, cmn_department, core_company) to populate reference fields with the correct sys_id values.
It includes error-handling logic based on the response from the ServiceNow Table API, with capabilities to retry failed operations or notify admins in real time in case of provisioning errors.
Given that the data is already fully transformed and validated, and no additional transformation is required on the ServiceNow side:
Is it best to continue using the Table API via the OOTB connector, or is there any benefit to switching to the Import Set API in this case?
From a security standpoint, we are planning to implement fine-grained ACLs and define role(s) specifically scoped to this integration. Are there any additional security best practices or considerations we should be aware of when using the Table API for such an integration?
We’re looking to align with ServiceNow best practices. Appreciate any insights or recommendations from those who’ve implemented similar integrations!
