Transform Map Overwrite Issue: Non-Empty Target Fields Not Replaced by Empty Import Set Values

[颯史小]

Please help identify the cause of the following issue:

When importing data from an Import Set table to the target table, existing non-empty fields are expected to be overwritten with empty values, but they are not being overwritten.

The Copy empty fields option is set to true in the Transform Map definition, so empty values should overwrite existing data. I have also verified that the incoming import data is indeed empty.

What could be preventing the overwrite with empty values?

[Ankur Bawiskar]

@颯史小 

do you have field map for that target field in your transform map? then only it works

see if source value is actually empty and doesn't contain any space character etc

is the target field readonly?

any before insert/update BR blocking from making it empty?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[颯史小]

@Ankur Bawiskar 

Thank you for answering my question. It seems the issue might be caused by a Business Rule, so I’ll take a look at that.

[Ankur Bawiskar]

@颯史小 

sure

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Tanushree Maiti]

Hi @颯史小 

To prevent an import from overwriting existing non-empty target fields with empty source values during a ServiceNow transform, you should 

1) Ensure the 'Copy empty fields' option is unchecked in the Transform Map configuration,

or

2) Using a field-level script to explicitly ignore blank source values

Use this script in the onBefore transform script (for all fields) Or Field map script (individual field)

if(source.u_field1 == '' ){

ignore = true;

}