Data doesn't get populated in the custom column of the import set table from data source

[Mahesh Bachhav]

I have created a custom import set table extended from Import Set Row. I have created custom columns in that import set table and assigned import_attribute_name to each column. I have also created a data source for that custom import set table. 

When I am importing(attaching) a JSON file to the data source, data is not populated to a custom column instead new columns are created "u_" prefix, and data gets populated into the new columns having the "u_" prefix.

The import_attribute_name value of the custom column and the newly created column with the "u_" prefix is the same.

Why data doesn't get populated in the custom column from the data source?

[Ankur Bawiskar]

Hi,

let the fields get created in import set

you can deactivate or delete the unwanted ones instead of creating custom field

Regards
Ankur

[Mahesh Bachhav · Accepted solution]

Below is my finding and solution for this problem - 

Findings - 

If column name and import_attribute_name values are exactly(case-sensitive) same then ServiceNow doesn't assign import_attribute_name value to column name.

In the below case value of column name and import_attribute_name is the status(lowercase) hence data wasn't populated.

I am not sure whether this is expected behavior of ServiceNow or a bug in it. 

Solution - Do not use the same value for column name and import_attribute_name. Either use a different value for column name or import_attribute_name value should be a different case. 

e.g.

• If I am using the "status" value for Column name then import_attribute_name should be Status or STATUS.
• If I am using the "status" value for import_attribute_name then the Column name should have some prefix (u_) or suffix(_u) to status or a different column name (status_val).