Robust transform maps

[sai bharath kas]

1)There are 2 Robust Transform Engine Entity Mapping, 1) imp to temp 2) temp to computer and in imp to temp Robust Transform Engine Entity Field Mappings there is no mapping on assigned to field but in temp to computer we have assigned_to-> assigned_to mapping, how is this possible when there is no assigned_to field on imp table.

(note that temp is not associated with any table)

2) How to restrict creation and updating records in table in robust transorm maps , can we use action=insert or update if yes where to use exactly

[Ankita_Patil]

Hello @sai bharath kas 

Answer to the Second Question :

Yes, RTE supports controlling whether records are inserted, updated, both, or skipped using the "Action" field in the Entity Mapping

In Robust Transform Engine, each Entity Mapping has an Action field (under the “Advanced” section)

You configure this here:

Go to: Robust Transform Engine → Entity Mappings

Open the desired mapping

Find the “Action” field in the form

Set to Insert or Update, or Ignore as needed.

Thank You !

Ankita Patil

[Ankita_Patil]

Hello @sai bharath kas,

Answer to the second Question -

Yes, Robust Transform Engine supports controlling whether records are inserted, updated, both or skipped using the "Action" field in the Entity Mapping

In Robust Transform Engine, each Entity Mapping has an Action field (under the “Advanced” section)

You can configure this :

Go to -> Robust Transform Engine -> Entity Mappings

Open the desired mapping 

Find the “Action” field in the form

Set to Insert or Update, or Ignore as needed.

Thank You !

Ankita Patil

[G Ponsekar]

Hi @sai bharath kas ,

To answer your first question

You're seeing a mapping for assigned_to from temp to computer even though assigned_to is not directly mapped in the imp to temp mapping. This is possible due to intermediate transformations or lookups within the Robust Transform Engine. 

Here's how it likely works:

• Intermediate Table (temp): The temp table (which is not associated with any specific table) serves as a staging or intermediary data structure where data from the import set (imp) is temporarily stored and transformed before being loaded into the target table (computer).
• Scripted Lookups or Entity Operations: Even if the assigned_to field isn't directly mapped from imp to temp, it can be populated in the temp table using scripted lookups or entity operations based on other fields.
• Example:
  • The imp table might contain a field like "User ID" or "Employee Number" instead of assigned_to.
  • An RTE Entity Operation or a transform script could be configured in the imp to temp mapping:
    • It could take the "User ID" from the imp table.
    • It could then use a GlideRecord query to search the sys_user table (or another user-related table) for a matching user based on that "User ID".
    • If a match is found, the script could then populate the assigned_to field in the temp table with the sys_id of the matching user.
• Final Mapping: Once the assigned_to field is populated in the temp table, it can then be mapped to the assigned_to field on the computer table in the subsequent temp to computer RTE Entity Mapping.

For second question, To control inserts and updates, use RTE Entity Operations with conditional scripts or by setting mapping conditions

If I could help you with your Query then, please hit the Thumb Icon and mark as Correct !!

Thanks, GP