Issue with Transform Map Creating Duplicate Columns

[monica190]

Hi Team,

I am facing an issue with a transform map. There is an OOB transform map for one of the HAM tables. The user has the option to download a template and execute the job.

For one of our requirements, we were asked to enable this functionality from the front end. To achieve this, I created a catalog form and set up a flow.

In the flow, I am creating a data source and reusing the same transform map, triggering a custom action to run it.

However, during this process, I noticed that new columns are being created, even when columns with the same display name already exist. The newly created columns have a backend name prefixed with "u_", despite having identical display names.

I want to prevent these duplicate columns from being created. Could someone advise on how to achieve this?

From the SS you can see 2 columns with Display name as Asset tag 

[Ravi Chandra_K]

Hello @monica190 

Is there a Coalesce on any field? You have to Create a coalesce on a unique field so that system doesn't create a duplicate record.

find more about coalesce below:

https://www.servicenow.com/community/itsm-forum/what-is-coalesce-explain-with-example/td-p/2341075

https://docs.servicenow.com/bundle/xanadu-integrate-applications/page/administer/import-sets/concept...

Please mark the answer as helpful and correct if helped.

Kind Regards,

Ravi 

[monica190]

hi @Ravi Chandra_K 

To clarify, the issue I am facing is not related to duplicate records but to duplicate columns. Specifically, when I run the transform map, new columns are being created in the target table, even if columns with the same display name already exist. The new columns have a backend name prefixed with "u_", although the display names are identical to the existing ones.

[ersureshbe]

Hi,

Please review the table to verify the new field and the "created by" entry. Does it correspond to the account name from the incoming transaction service account? If so, kindly examine the transformation script to identify any code responsible for generating a new field, which should begin with 'u_'. There should be a clue present to help identify the issue.

[monica190]

hi @ersureshbe 

when I check the dictionary entry for these newly created columns, it shows my name as the creator. This confirms that the columns are being created as part of the data load I am performing.