Prevent Overloading CIs from Excel Service Graph Import and importance of Data Source History
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Dear ServiceNow Community,
Seeking some advice in setting up reconciliation rules and data precedency and understand how important is the Data Source History during reconciliation.
In our current environment, we have 2 discovery sources to update the list of computers as stated below:
- ServiceNow to run network discovery and create/update the computers, which are later manually updated on UI with 'Assigned To' and 'Support Group'.
- Excel ServiceGraph Import to manually upload the offline computers not connected to network.
Requirement: The fields 'Assigned To', 'Support Group' in the ServiceNow discovered computers, which were manually updated on UI, should NOT be overwritten/overloaded by 'Excel Import'.
To fulfil this requirement, we have the data precedence set in 2 reconciliation rules on Computer Table:
- ServiceNow -> Priority (100)
Attributes -> Hostname, IP Address, Class, OS, Assigned To, Support Group etc.
Filters -> Created by Excel Import = FALSE - Excel Import -> Priority (200)
Attributes -> u_Display_Name
Filters -> None (No filters)
Challenge: The IRE data precedence is not preventing the overloading of CIs.
Does this have to do anything with the entries not being present in data source history (cmdb_datasource_last_update), given that these attributes are manually updated on UI?
