What is difference between 'RTE Entity fields' vs 'RTE field mapping' in IH-ETL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2024 11:32 AM - edited 07-04-2024 03:10 AM
What is difference between 'RTE Entity fields' vs 'RTE field mapping' in IH-ETL? as I see different number of attributes in both the tabs for same TARGET table.
I need to know which fields finally gets mapped to target table? Those 16 fields or the 13 fields?
Please dont copy paste answers from ChatGPT or any other AI tools 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2024 12:18 PM
Hi @Suggy ,
Below explanation might help you with your queries:
In ServiceNow's IntegrationHub ETL (Extract, Transform, Load), there are different components used to handle real-time event (RTE) data. The 'RTE Entity fields' and 'RTE field mapping' are both important parts of this process, but they serve distinct purposes. Here’s a breakdown of the differences between these two:
RTE Entity Fields
RTE Entity Fields are the fields that define the structure and schema of the real-time event data entities. These entities represent the data objects or records that are being transferred and processed in real-time through IntegrationHub ETL.
- Purpose: Define the schema and structure of the data entities for real-time events.
- Usage: Specify the fields and data types that make up the real-time event entities.
- Example: For a real-time event representing a Change Request, the RTE Entity Fields might include fields like number, short_description, priority, state, etc.
RTE Field Mapping
RTE Field Mapping refers to the mapping between the source fields (from the event data) and the target fields (in ServiceNow or another system). This mapping ensures that the incoming real-time data is correctly transformed and loaded into the appropriate fields in the target system.
- Purpose: Define how data from the source system fields maps to the target system fields.
- Usage: Configure the transformation rules and mappings to ensure data is accurately transferred and transformed.
- Example: If the source system has a field incident_id that needs to map to the number field in the ServiceNow Incident table, the RTE Field Mapping will specify this correspondence.
Key Differences
Definition vs. Mapping:
- RTE Entity Fields: Define what fields exist in the data entities.
- RTE Field Mapping: Define how the data from these fields is transferred and transformed.
Schema vs. Transformation:
- RTE Entity Fields: Concerned with the schema and structure of the entities.
- RTE Field Mapping: Concerned with the transformation and mapping of data between source and target fields.
Configuration Focus:
- RTE Entity Fields: Focus on setting up the data model for real-time events.
- RTE Field Mapping: Focus on setting up the rules for how data moves from the source fields to the target fields.
Thanks.
Hope it helps.
If my response turns useful please mark it helpful and accept it as solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2024 01:06 AM
@HrishabhKumar May I know the source of this info please?