Incorrect Mapping for Reference Field in Robust Transform Map

[DebjitGhosh31]

Hi,

I am using Robust Transform Map to map data source to CMDB computer table. 

Now, we have a mapping for Manufacturer information where staging contains a string (manufacturer name), what I am doing is checking ServiceNow core_company table if the manufacturer present or not (via name) and if present then returning SysID of the record. Then I have mapped the SysID with CMDB Computer table's 'manufacturer' field (it's a reference field to core_company). But what's happening is instead of referencing the correct record, it's creating another record where name = SysID and referencing that one.

It's an odd issue and I am unable to figure out why it's happening as usually passing sysid to reference field is the way to go.

Please suggest.

Regards,

Debjit

[Ankur Bawiskar]

@DebjitGhosh31 

share the relevant scripts along with screenshots.

Is this happening with every row in import set?

[DebjitGhosh31]

Hello @Ankur Bawiskar ,

There's no script involved as it's an one to one Entity mapping using Robust Transform Engine.

Here the source field is a string field contains SysID and target field is a reference field which should use the SysID to reference to the correct item. 

But instead of that it is creating a new record with SysID as the item.name. [Probably as coercion action = create which is causing the creation.]

Not able to understand why passing sysid to a reference field is giving this unexpected result.

Regards,

Debjit

[Ankur Bawiskar]

@DebjitGhosh31 

can you share screenshot?

[MarcinM]

Hello,

I had similar issue when using RTE. The case is you need to slightly enhance your ETL Entity fields for the table that will be used.

From the record (GlideRecord) perspective indeed core_company is a reference field but remember that RTE is using IRE and JSON Payloads so you need so specify the reference field's sys_id as well.

Regards,

Marcin