- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2014 08:13 AM
Why would this be happening? I'm trying to import open incident records from my production SN instance to our development instance.
I followed the steps in Importing from Another ServiceNow Instance - ServiceNow Wiki and I keep getting the above error and the table isn't being createad.
The Import Set Table Name is a unique table name, and this is the file path: /incident.do?XML&sysparm_query=active%3Dtrue%5Estate%3D1 - which if I run it via a direct web service is a valid query.
Help?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2014 07:28 AM
I figured out my own issue. I didn't have the correct XPath selected. For some reason, it didn't work when I entered xml//incident, but did work when I entered //incident. I would have thought the former would work!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2014 07:28 AM
I figured out my own issue. I didn't have the correct XPath selected. For some reason, it didn't work when I entered xml//incident, but did work when I entered //incident. I would have thought the former would work!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2015 04:58 AM
Allow me to bump this thread - I encountered this problem today working on LDAP imports. After some ranting I found out there was an error in my LDAP filter.
So for anyone who is facing this - I think it's safe to say that one possible reason for "Import set not created" is that you have a faulty data source which can be loaded, but is not providing any data.