Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Limit Service Graph Connectors to 'Update'

JasonW39
Tera Contributor

Good Morning,

My organization has several Service Graph connectors setup with overlapping (sometimes conflicting) data, and I'm finding that, while I can use Reconciliation Rules to prioritize specific attributes, I'm not sure I can stop a specific data source from creating records altogether if they don't already exist.

 

For example:

SGC-A (source of truth) finds and creates 100 server records and has priority 100 for all attributes

SGC-B has priority 200 but finds an additional 10 servers that were not found by 'A' because they are not in a production environment

 

I would like SGC-B to provide supplemental information for records created by A (particularly for attributes that SGC-A does not have access to), but I do not want it to create new records.

My initial thought is to remove the mapping of key attributes (based on Identification Rules) in the ETL, however, I don't know if that will work, and I'd like to find a cleaner way to accomplish this if possible.  Any advice is appreciated.

1 ACCEPTED SOLUTION

AJ-TechTrek
Giga Sage
Giga Sage

Hi @JasonW39 , 

 

Correct me if I am wrong, you want to stop to creating new record using the Service Graph connector B, In that case that can be achieved using the Identification rules only.

 

Also you need to create the filer condition in Identifier entries or Identification rule if that condition matched, it will not created the record in table and only update the existing records.

 

Also you can create the transform maps scripts to do not create the records the in target table.

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

 

Thank You

AJ - TechTrek with AJ

Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/

YouTube:- https://www.youtube.com/@learnitomwithaj

ServiceNow Community Rising Star 2024

View solution in original post

In this video i have explained about Web service integration in ServiceNow like how it works, how we can configure it, what are the prerequisite and many more. I have covered below topics in this video. 1. understand Web Service. Like when and how we will use it. 2. Talked about Inbound and ...
2 REPLIES 2

AJ-TechTrek
Giga Sage
Giga Sage

Hi @JasonW39 , 

 

Correct me if I am wrong, you want to stop to creating new record using the Service Graph connector B, In that case that can be achieved using the Identification rules only.

 

Also you need to create the filer condition in Identifier entries or Identification rule if that condition matched, it will not created the record in table and only update the existing records.

 

Also you can create the transform maps scripts to do not create the records the in target table.

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

 

Thank You

AJ - TechTrek with AJ

Linkedin:- https://www.linkedin.com/in/ajay-kumar-66a91385/

YouTube:- https://www.youtube.com/@learnitomwithaj

ServiceNow Community Rising Star 2024

In this video i have explained about Web service integration in ServiceNow like how it works, how we can configure it, what are the prerequisite and many more. I have covered below topics in this video. 1. understand Web Service. Like when and how we will use it. 2. Talked about Inbound and ...

JasonW39
Tera Contributor

For anyone who comes across this looking for a simple answer:

 

Using the 'IRE Data Source Rules' I was able to create a rule for a specific CI class, simply check the box for "insert not allowed" and choose the Service Graph Connector as the data source.