"Import Set not Created, invalid target table" with CSV File

[Brizky]

Hello, folks.

I'm wondering if anyone can explain to me why I'm getting this error.  I've created a data source for an import.  I've also created a transform map.  When I try to execute the import, I get an error that my target table is invalid.  But what's confusing is that the "target" table specified in the error is actually the SOURCE table that I assumed would be the STAGING TABLE.  And my target table is actually the User table in ServiceNow.

The CSV file I'm using for this import is stored on a share.

Now, I thought that ServiceNow was supposed to create the staging table itself and you just tell it what the name of the table should be.  So the fact that the staging table is 1.) invalid and 2.) listed as the target table makes no sense to me.

Initially, I thought that the staging table WAS the target at some point, with the CSV file being the source.  And maybe ServiceNow couldn't get to the share to populate the staging table so that IT would then be the source.  but if that were the case, shouldn't ServiceNow say something like "couldn't access the file" or something?

[Harsh Vardhan]

Hi @Brizky - Looks like data is not accessible, double check if you add as an attachment on data source does it create the staging table with those data if it does then your file was not accessible before ?

[Brizky]

Thanks for responding, Harshvardhan.  You mentioned "adding an attachment" which made me go back to my data source set up.  My File Retrieval type is attachment and I specified the path of the file. 

I'm just now seeing that there's a button to add an attachment.  In my head, I thought I had to tell ServiceNow the path and it would ADD the file as an attachment when I saved my data source.  

And NOT doing this could explain why, when I tried to do my field mappings, there were no fields to choose from in the source field dropdown and why I couldn't specify it directly.😆

I'm going to try adding the attachment now.  And if it works I'm going to be both happy and mad. 😂

[Harsh Vardhan · Accepted solution]

Field mapping will work once the column would get created in staging table else you wont find. 

1. Add attachment on data source
2. Load 20 records so you can validate those data is coming into staging table or not.
3. Start field mapping because you have data in staging table with attributes which you wanna map with user table.
4. after mapping load all records to test if it does any magic on user record .

Hope it will help you.

Thanks,

Harsh

[Brizky]

THAT WAS IT!  I had to load data in it.  Again, that was something I thought ServiceNow would do automatically when i tried to run the import.  But I can now see the field values when i try to field map.  I think that was the issue.  

THANK YOU !!!