
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2022 11:26 AM
We want to block Discovery from changing the Manufacturer and Model.
For example, if we have a desktop Computer of DELL Optiplex 7020 MT we don't want Discovery resetting it to
Dell Inc. OptiPlex 7020 .
I created an IRE rule on Hardware (and on Computer, both with no effect)
and
but Discovery, in the Creating CI phase, overwrites it back to Dell Inc. OptiPlex 7020 .
What am I doing wrong here?
Thanks!
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2022 07:04 PM
Hi
It looks like you have create a single reconciliation rule there, so when you add both Manual and ServiceNow, they are authorised to update the same list of attributes.
You could change this to create two separate rules, the first one just for Manual which is allowed to update all attributes, and then a second one for ServiceNow which can only updated the attributes that you choose.
If Manual has a higher priority, it should prevent ServiceNow from overwriting the value if it has already been populated (If you allow ServiceNow to update all attributes also)
Hope this helps
Regards,
David

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2022 07:04 PM
Hi
It looks like you have create a single reconciliation rule there, so when you add both Manual and ServiceNow, they are authorised to update the same list of attributes.
You could change this to create two separate rules, the first one just for Manual which is allowed to update all attributes, and then a second one for ServiceNow which can only updated the attributes that you choose.
If Manual has a higher priority, it should prevent ServiceNow from overwriting the value if it has already been populated (If you allow ServiceNow to update all attributes also)
Hope this helps
Regards,
David

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2022 11:28 AM
David, thanks your response is basically correct, but found out some additional things I was doing wrong
- Discovery Source=Manual Entry is apparently useless in an IRE Rule, as the engine is not invoked for manual entry
- I had created the rule for Hardware, as that would include Computers and Servers, however, there are specific Configuration fields that are not selectable at the Hardware lever, but are at the Computer level, such as Operating System and OS version - I wanted to ensure that imports cannot update those values, only ServiceNow, but you cannot do that if the Recon rule is created at the Hardware level of the hierarchy. When I tried to create a Recon rule at Computer, it would not allow me to save, as it said it conflicted with the Hardware level rule, which is higher up in the hierarchy.
So, I deleted the Recon rules at Hardware, and rewrote them as noted above at Computer.
There may be other ways to accomplish this, but this is what worked for me.
It's unfortunate that neither the ServiceNow site nor various YouTube videos seem to explain this level of detail.
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2022 03:43 PM
Thanks for the update David, I didn't think about the fact that manual entry probbaly did not come through IRE. Glad you managed to get it sorted out.
Cheers,
David