- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2016 04:11 PM
I have mostly used the Import set API for loading data into ServiceNow. Often times, I need to do this because I have a script that will run in SN to prep and transform the data. However, for some of my loads, it may be a better approach to use the Table API instead. I'm thinking I may get some performance improvements since it wouldn't have to go through a transformation process. But, I need the coalesce feature so I don't create duplicates. Does the Table API have this? I don't see it mentioned in the documentation and my basic tests indicate it doesn't exist.
Second part to my question is what is the MOST efficient way to pump a lot of data into SN using the Rest API? The only performance approach that looks like will help is using the X-No-Response-Body set to true which saves some data from being sent back. I need more than this because it's taking close to 1 second per transaction and when I have 40,000 of these, it's running 1/2 day long. It needs to remain as a Rest API though as the data is remote and sent through a program with Rest API. Thanks!!!!
Todd
p.s., I should also add that I'm following this recommendation as well but still need further perf improvements if possible. http://wiki.servicenow.com/index.php?title=Troubleshooting_Import_Set_Performance#gsc.tab=0
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2016 04:09 AM
Hi Todd,
For Importing bulk data with coalesce requirement rest import set API is the way to go. If you want to improve perf suggestion is to turn off business rules on transform maps if possible, another tip is to make sure the import set cleanup jobs are running to keep import set tables small. We are looking at enhancing async import set rest API processing to improve this as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2018 05:15 AM
I recommend you either use an import set API and determine what you are using to coalesce, or use the PATCH (not POST or PUT) to update the record. You might find this article helpful....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2018 06:25 AM
Thanks Chuck for information, I tired in another way, by making field unique and done the POST REST api , it is working like coalesce. That prevent from creating duplicates.
Thanks,
Ashok.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2018 07:19 AM
Good to know. Thanks for sharing.
