- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2021 10:45 AM
Hello,
I am working on Integrating Cisco Collector with ServiceNow via the IntegrationHub ETL. I have the REST API's for getting data from Cisco Collector, the Oauth app has been registered and also can successfully get the token.
The error I am seeing is when I open the ETL Transform Map that is supposed to pull in the data from the import sets. I constantly get the following error "There was an error with the partial preview API." and then subsequently step 2 which is "Prepare Source Data for Mapping" shows no data. I have not found any forums or documentation that is relevant to this error.
Would really appreciate your help on this.
Thanks!
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2021 09:02 AM
The issue has been resolved. The integration lost some of it's a mappings after moving the update set to prod and hence started throwing the error. I just reloaded the old update sets, committed them one by one and then remapped the fields. That fixed the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2021 09:02 AM
The issue has been resolved. The integration lost some of it's a mappings after moving the update set to prod and hence started throwing the error. I just reloaded the old update sets, committed them one by one and then remapped the fields. That fixed the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2021 08:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2021 05:58 AM
Hello Varun,
I am having the same issue but with a fresh ETL Transform Map that has no mappings whatsoever. I have repeatedly re-created it using slightly different settings to no avail. What exactly did you do to make the error go away, besides remapping the fields?
Thank you,
Erik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2021 04:45 AM
I had a perfectly working ETL map and suddenly saw this exact error pop up.
I did two things:
- made a new import set (on the Data Source)
- activated the ETL.
I don't think the new import set fixed it, but activating made a difference. The mappings reappeared and the error was gone.