Transform maps loading more than the excel data

[Nisha30]

Hello Experts,

One of our table is empty. Hence we are loading data from excel sheet  via Transform maps (Load Data)

Since there are many duplicates in many fields hence NO COALESCE = TRUE in our transform map, since we want to load all data (around 3k)

In staging table the data is correct however post transform the records are trippled around 9k.

why it is increasing it can simply insert the number of records in the staging .

Anyone faced similar issue .

Thanks

[Rakesh_M · Accepted solution]

Hi @Nisha30 ,

Here are a few possible reasons that come to mind:

• In the Transform Map record, under the Field Maps related list, set the Choice action to Ignore.If you have a field that references the same table, it may create new records during the transform.

• During the transform, make sure there is only one Transform Map in the "Selected Maps Run in Order" bucket.

• Check whether you have configured any Transform Scripts.

• Review the Import Set records after the transform to see how the data is being processed.

Could you please share more details about your issue? This will help us better understand the problem and suggest the appropriate solution.

Also, try importing just 1 or 2 records first and observe the behavior. This can help narrow down the root cause.

[Nisha30]

Thankyou everyone for assisting learning lot from community .

Just to know what we did is CHOICE= IGNORE , that made it work without any Coalesce true.

[Rakesh_M]

Hi @Nisha30 ,

Glad you got it working.

To explain why Choice Action = Ignore fixed the issue:

Suppose you're importing the following records:

 

Number	Short Description	Parent Incident
INC0000001	Internet is down	INC9000001
INC0000002	Zoho is down	INC9000002
INC0000003	Teams not responding	INC0000001

Here, INC9000001 and INC9000002 are reference records to same table (Parent Incident values). They are not part of the import data itself.

If the field map's Choice Action is set to Create, and  if ServiceNow cannot find those referenced records, it attempts to create them automatically. As a result, instead of importing only the 3 intended incidents, you end up with 5 records:

• INC0000001
• INC0000002
• INC0000003 (INC0000001 is not created again, referenced to 1st record)
• INC9000001 (auto-created)
• INC9000002 (auto-created)

Setting Choice Action = Ignore prevents ServiceNow from creating new referenced records, which is why the duplicate/unexpected records are no longer created.

[OlaN]

Hi,

You might have empty rows in your Excel sheet, which gets transformed into empty records.
Is the property "Create new record on empty coalesce fields" checked in your transform map ?
If so, what happens if you uncheck it?