Import Sets - Importing creating new copies of existing fields.

[raprohaska]

Maybe someone out there has seen this before or maybe I’m just being really slow today. When using the standard “Load Data” feature of ServiceNow and targeting an existing Import Set table that it loads to.

These are the key fields that belong to the table:

 

Here is a sample of the file we are using to load into the import set table. The column names match the field labels of the staging table:

 

Using the OOB Load Data, the import set table is selected, along with the pre-mentioned file:

 

I did not transform the data, so the Transform Map doesn’t come into play. We noticed that the “value” field was blank after the load. After searching a bit, we noticed that there were two “Value” fields. The following screen shot shows there was a new set of fields created when I imported. They were created by me at the time of the import and contain the values from the sheet.

I have not seen these before and I have done a lot of imports. Having said that, my mind is going blank and am not sure if it is column header naming issue or column order issue or a scoped application issue... I feel like I’m missing something simple.

Thanks for any help you can give,

AA

[Abhinay Erra]

Usually the fields are created with u_ perfix whenever data is loaded in to the table. Did you create the fields without prefix 'u_' manually? I 

[raprohaska]

It is a scoped application provided via a vendor. Scoped applications don't get a "u_" prefix. They have not seen this reaction before and are also looking into it. But our need is now so trying to help debug the issue.