Rakesh_M
Mega Sage

‎07-21-2026 06:12 AM

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.

View solution in original post

Nisha30
Mega Sage
In response to Rakesh_M

‎07-22-2026 07:58 AM

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.

0 Helpfuls

Rakesh_M
Mega Sage
In response to Nisha30

‎07-23-2026 10:30 AM

Hi @Nisha30 ,

Glad you got it working.

To explain why Choice Action = Ignore fixed the issue:

Suppose you're importing the following records:

 
NumberShort DescriptionParent Incident
INC0000001Internet is downINC9000001
INC0000002Zoho is downINC9000002
INC0000003Teams not respondingINC0000001

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.


0 Helpfuls

OlaN
Tera Sage

‎07-21-2026 06:37 AM

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?

 

Tanushree Maiti
Tera Patron

‎07-21-2026 08:23 AM

Hi @Nisha30 

 

  • Check for Multiple Transform Maps: Navigate to System Import Sets > Transform Maps. Filter by your staging table name to check how many Transform Maps are active for that specific Import Set . Refer: KB0747613 When importing data, some staging table records are duplicating or an Import set row is du... 
  • If you have multiple maps, verify which one is the correct mapping and ensure the others are deactivated so they do not process the same staging rows.

  • For the records that should be created, ensure that:

    1. The Choice Action on your field maps is set to "create" if you want new records.
    2. You do not have Business Rules, Inbound Actions, or onBefore/onAfter Transform Scripts that are inserting duplicate or cascading records

     

0 Helpfuls