Reconciliation rule working for a field but not for the other
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2023 07:04 AM
Thanks in advance for you help on the matter!
I need to exclude some fields from discovery scope of Cloud Resources (already did CAPI migration)
In particular, Virtual Machine Instances fields "Location" and "Fully Qualified Domain Name" must be filled through a daily scheduled script with values taken from some key values.
Obviously, discovery and script will constantly override one another (don't know if it helps, but discovery puts empty value in fqdn)
I've implemented some Reconciliation rules as shown below,
The expected result should be, after a first run of the script, that Location and FQDN values should not be changed by discovery.
This works for Location, but FQDN is still emptied after a discovery run.
Can someone guess why this happens? It's strange because for Location works but not for FQDN, even if the reconciliation rules are the same.
I've also tried putting both fields in the same reconciliation rule, or removing the second rule for ServiceNow source, but the result is still the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2023 07:20 AM - edited 11-20-2023 07:20 AM
Is the FQDN attribute excluded from your ServiceNow Discovery Reconciliation rule? Also - be sure that ServiceNow is the source that is actually updating the FQDN attribute, note that Credentialess Discovery is also a valid source.