Service Graph Connector for Intune

Fatima S Sayyed
Tera Contributor

‎02-09-2024 04:34 AM

Hi, does anyone have an article / document that explains how exactly the data is being processed within ServiceNow after being imported.

I am aware that it is transformed using RTE and refers to Device ID as an unique identifier i want to understand the sequence of it.

0 Helpfuls
  • 1,442 Views
5 REPLIES 5

Fatima S Sayyed
Tera Contributor
In response to Prashant Ahire

‎02-12-2024 12:43 AM

@Prashant Ahire thanks but i've already taken a look at the links you mentioned and none of it explains the processing 🙂 

0 Helpfuls

Rajdeep Ganguly
Mega Guru

‎02-12-2024 02:20 AM


Sure, I can explain the sequence of how data is processed within ServiceNow after being imported. Here's a simplified version of the process:

1. **Data Source**: The first step in the data import process is to define a data source. This is where you specify where the data is coming from. This could be an external database, a file, or a web service.

2. **Import Set Table**: Once the data source is defined, an Import Set Table is created. This is a staging area where the data is initially loaded into ServiceNow.

3. **Transform Map**: A Transform Map is then created to map the fields from the Import Set Table to the target table in ServiceNow. This is where you define how the data from the source is transformed into the format required by ServiceNow.

4. **Run Transform**: The Transform Map is then run, which loads the data from the Import Set Table into the target table in ServiceNow. This is where the actual data import happens.

5. **Coalesce Fields**: During the transformation, ServiceNow uses coalesce fields to determine if a record in the Import Set Table matches an existing record in the target table. If a match is found, the existing record is updated. If no match is found, a new record is created. By default, ServiceNow uses the sys_id field as the unique identifier, but you can specify other fields as coalesce fields.

6. **Data Lookup and Record Matching**: ServiceNow uses data lookup rules and record matching to further refine the data import process. This can include things like data cleansing, data normalization, and data enrichment.

7. **Post-Import Processing**: After the data is imported, there may be additional post-import processing that needs to happen. This could include things like running business rules, triggering workflows, or updating related records.

8. **Error Handling**: Throughout the data import process, ServiceNow has robust error handling capabilities. If there are any issues with the data import, ServiceNow can log the error, send an email notification, or even stop the import process.

9. **Reporting and Auditing**: After the data import process is complete, ServiceNow provides comprehensive reporting and auditing capabilities. This allows you to track the success of the data import, identify any issues, and ensure data integrity.

Remember, this is a simplified version of the process. The actual process can be much more complex, depending on the specific requirements of your data import.


nowKB.com

For asking ServiceNow-related questions try this :
For a better and more optimistic result, please visit this website. It uses a Chat Generative Pre-Trained Transformer ( GPT ) technology for solving ServiceNow-related issues.
Link - https://nowgpt.ai/

For the ServiceNow Certified System Administrator exams try this :
https://www.udemy.com/course/servicenow-csa-admin-certification-exam-2023/?couponCode=NOW-DEVELOPER

0 Helpfuls

Fatima S Sayyed
Tera Contributor
In response to Rajdeep Ganguly

‎02-16-2024 11:22 PM

Rajdeep by processing i meant Intune data flow and not how the oob processing works 🙂 

For Intune we have a staging table and then we also have a related table that is used in IRE hence my question about the flow.

0 Helpfuls