Transform map field is empty in Staging table

preethigovi
Tera Contributor

Hi Team,

Transform map field is empty in import set table.

What could be the reason?

preethigovi_0-1733841819040.png

 

1 ACCEPTED SOLUTION

Hi @preethigovi,

 

You can absolutely have more than 1 Transform Map associated to a data source. There is no 'impact' what-so-ever. When multiple Transform Maps are associated, you'll just need to decide which Transform Map to use...

If any automation has been set up etc (this is based on any configuration made on your instance), then you'll just need to make sure this is considered (selecting the appropriate Transform Map).

 

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.





Thanks, Robbie

View solution in original post

5 REPLIES 5

Robbie
Kilo Patron
Kilo Patron

Hi @preethigovi,

 

Would you mind clarifying a few point please so as to help.

Can you confirm which table you're referring to when you state the 'Import set table' please.

The ServiceNow defined import set table ('sys_import_set') doesn't actually have a column named Transform Map.

 

I believe you're referring to the staging table that is created when you load the data - correct? On initial load of the data, the Transform Map field will be empty. Once a Transform Map has been created and associated to the staging table via the Transform Map 'source table' field, and then importantly ran - only then will you see the Transform Map field populated within the staging table.

 

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.





Thanks, Robbie

@Robbie  We are pulling data from workday using import set it transform to target table. On particular during this stuck and transform field in sys_import_set got emptied

 

I have another query, can 2 transform map run on same import table concurrently? What will be impact 

Hi @preethigovi,

 

You can absolutely have more than 1 Transform Map associated to a data source. There is no 'impact' what-so-ever. When multiple Transform Maps are associated, you'll just need to decide which Transform Map to use...

If any automation has been set up etc (this is based on any configuration made on your instance), then you'll just need to make sure this is considered (selecting the appropriate Transform Map).

 

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.





Thanks, Robbie

@Robbie  Thank You.

 

I have another query, example i have termination reason field coming into staging table but i don't want that particular to be inserted to target table field.

Like it must sit on staging table but not transform to target how to achieve this?