Robust Import Set Transformers

[HS7]

Hi

What is the difference between the normal method of importing using a transformation map and Robust Import Set Transformers?

Do I need to define an import set table for Robust Import Set Transformers?

Thanks in advance.

[YaswanthKurre]

Hi Hs,

Robust Import Set Transformers are generally preferred over traditional Transform Maps when extracting, transforming, and loading data into multiple target tables, due to their flexibility and efficiency.

Transform Maps

• Designed to map data from a staging table to a single target table.

• To load data into multiple tables, you must create separate transform maps, each performing its own read operation.

• This approach can lead to redundant processing and reduced performance.

Robust Import Set Transformers

• Provide separated transformation and processing logic, offering greater control and modularity.

• Enable data to be extracted once, stored in an intermediary structure, and then transformed and distributed to multiple target tables.

• Improve performance by:

  • Processing in batches, reducing resource usage.

  • Minimizing reads, as one read can support multiple target table writes.

Please refer the product documentation : https://www.servicenow.com/docs/bundle/yokohama-integrate-applications/page/administer/import-sets/c...

Please mark this as helpful and correct if this answers your question.

Thanks,

Yaswanth

[Abbas_5]

Hello @HS7,

In ServiceNow, Robust Import Set Transformers (RTE) and standard Transform Maps both facilitate data import but with key differences. While Transform Maps handles both transformation and processing in a single step, RTE separates these functions, offering greater flexibility and scalability for complex data loads, particularly when dealing with multiple target tables and complex data structures. Yes, you need to define an import set (staging) table for robust import set transformers as well. 

Here's a more detailed breakdown:

1. Standard Transform Maps:

• Functionality:

  Transform Maps handle both the transformation of data and the transfer of data to the target table in a single step. 
• Flexibility:

  Limited in terms of handling complex data structures or scenarios where you need to process data in multiple stages before reaching a target table. 
• When to use:

  Suitable for simple data imports where you need to map data from the import set to a single target table with straightforward transformations. 

2. Robust Import Set Transformers (RTE):

• Functionality:

  RTE separates the transformation and processing steps, allowing for more complex data manipulation and data flow. 
• Flexibility:

  Offers more flexibility in handling data, particularly when dealing with complex data structures, multiple target tables, or when you need to perform multiple transformations before loading data into the target tables. 
• When to use:

  Recommended for complex data imports, data loads to multiple target tables, or when you need to perform multiple transformations or processing steps before loading data. 

3. Import Set Table (Staging Table):

• Requirement:

  Both standard Transform Maps and RTE require an import set table (staging table) to hold the incoming data before it's processed and transformed. 
• Purpose:

  The import set table acts as a temporary storage area for the data, allowing you to define the transformations and mappings before applying them to the target table. 

In essence:

• If you have a simple data import and need to map data to a single target table, a standard Transform Map might suffice. 
• If you have complex data, need to process data in multiple steps, or need to load data into multiple target tables, RTE offers greater flexibility and control. 
• In both cases, an import set table (staging table) is required to hold the incoming data. 

Key Differences in a Table:

Feature	Standard Transform Map	Robust Import Set Transformer (RTE)
Functionality	Transform & Process	Separate Transform & Process
Complexity	Limited	High
Data Flow	Single Step	Multi-Step
Target Tables	Single	Multiple
Import Set Table	Required	Required
Flexibility	Limited	High
When to use	Simple Imports	Complex Imports, Multiple Targets

OR refer to the link below:
https://www.servicenow.com/docs/bundle/yokohama-integrate-applications/page/administer/import-sets/c...

If this is helpful, please hit the thumbs up button and accept the correct solution by referring to this solution in the future; it will be helpful to them.

Thanks & Regards,

Abbas Shaik

[HS7]

Thank you  @Abbas_5 .

I don't understand how transformation and processing are separated in the RTE.
Is there a diagram that shows how transformation and processing are separated?

And what exactly does processing refer to?

[Harish Bainsla]

Hi @HS7 check below link to clear your question it explain in a good way 

https://servicenowwithrunjay.com/robust-transform-engine-vs-transform-maps/

https://youtu.be/8B-mf3FmDfc?si=4sQvtVi_VYawe9uR

if my answer helps mark helpful and accept solution