Import Set – Unable to populate field during transform (Robust Transform Map)

[siddheshagn]

Hello Community,

I am facing an issue in ServiceNow where a specific target customized field is not getting populated after an Import Set transform runs, even though the source data is correctly visible in the Import Set table.

I have written a script include where I want the newly customized field to be populated basis on the existing value which will come after the third party sends the data, the data is reaching to import set table after that basis on the incoming data we have to set the value.

Earlier I have called the script include in data source itself, but it didn't work as expected. Also, I am trying to call the function in post import currently. I have applied logs to check it as of now.

Not sure it will work as expected or not.

I am yet to try for below :- 

1) pre-import Schedule data import

2) sys_rte_eb_etl_definitions 
3) cmdb_inst_application_feed

Tried with data source & post import script in scheduled data import as of now.

Environment Setup

• Data Source → Import Set table → Transform Map → Target table

What I Am Looking For

1. Additional debugging steps — transform history logs, gs.log usage, etc.

2. Any common configuration pitfalls causing a single field to be skipped.

3. Known KB articles or product behaviors related to this issue.

[vaishali231]

hey @siddheshagn 

Since the data is visible in the Import Set table, the data source and load process seem to be working correctly. The issue is most likely occurring during the transform phase. You may want to check the following:

1. Transform History
   Go to  Transform History.
   Open the latest transform run.
   Review the Transform Log and Row Log for any skipped field messages or script errors.
   
2. Field Mapping
   Verify the field map in the Transform Map.
   Ensure the source column name exactly matches the Import Set column.
   Confirm it is mapped to the correct custom target field.
   
3. Script Include Usage
   If a Script Include is used, confirm it is being instantiated correctly.
   Example:
   

var helper = new CustomHelper();
target.u_custom_field = helper.getValue(source.u_source_field);

4 . Quick Debug Test

     Temporarily assign a static value in the transform script:

target.u_custom_field = "test";

If the value populates, the issue is likely within the Script Include logic.

5.  Logging

Add logs in the transform script to confirm the source value is available.

gs.log("Source value: " + source.u_field_name);

  6. Business Rules / Flows

      Check if any Business Rules, Flows, or Scripts on the target table are updating or clearing the field after       the  transform.
7 .  Script Location
    Transformation logic typically works best in onBefore or onAfter Transform Map scripts rather than in the Data Source or post-import scripts.

*************************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

[siddheshagn]

Hi @vaishali231

As I mentioned I am using Robust Transform Map and Integration Hub ETL for populating CI using updating or creating CI. Since I am populating some value in my newly created custom field in import set table which gets populated after third party send the data to import set table and currently, I have called my script include in post processing schedule data import but as per my understanding in post processing the data will already reach target tables of cmdb which I don't want to happen . While transformation it should consider the value of my field and then reach target table.

Regards,

Siddhesh Agnihotri.

[siddheshagn]

Hi @vaishali231,

As mentioned, I am using Robust Transform Map basically and ServiceNow ETL to update CI's my objective is I am populating a newly created custom field on the import set table which is getting populated after Third Party Sends the Data but I currently I am suspecting that field is not getting used in transformation. Since the newly created field is being used as a condition in creating or updating CI's.

Currently I called my script include which is helping in populating that custom field is called in Schedule Data Import Post Import Script which usually works after the CI's get updated as per my understanding.