Partial API Error in IntegrationHub ETL

Varun M
Mega Contributor

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!

1 ACCEPTED SOLUTION

Varun M
Mega Contributor

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.

View solution in original post

6 REPLIES 6

Varun M
Mega Contributor

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.

Diljith
Tera Contributor

Hi Varun,

I am also facing similar issue while using ETL. As per your suggestion i tried remap fields. but i am getting below screen which is not allowing me to map fields.

find_real_file.png

Can you please specify in detail how you mapped the fields?

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

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.