Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Reconciliation rules configuration

SAIRSM
Tera Contributor

HI all,
Currently I need to configure a reconciliation rule to update the serial number of a windows user as manual entry as while discovery it is taking baseboard serial number instead of system serial number, so here i have to update the system serial number manually and have to make it is not overridden when discovery runs.
For this, I created a manual entry rule with low priority and also high priority but nothing works.
Anyone, could you please what is the best way to overcome this situation.
Thanks,
Rama Satya Sai M

9 REPLIES 9

pr8172510
Kilo Sage

Hi @SAIRSM,

Yes, Reconciliation Rules are the correct approach to prevent Discovery from overwriting the manually corrected serial_number.

Create/configure a reconciliation rule for the relevant Windows CI class and specifically the serial_number attribute:

  • Manual Entry → higher priority
  • Discovery → lower priority
  • Attribute → serial_number

Smaller priority numbers have higher precedence. Once the authorized Manual Entry source updates the attribute, a lower-priority Discovery update will be rejected.

Also check whether an existing attribute-specific rule or dynamic reconciliation rule is overriding your rule. An attribute-specific rule takes precedence over an "Apply to all attributes" rule, and a dynamic reconciliation rule takes precedence over static reconciliation rules.

After enabling the rule, check Data Source History (cmdb_datasource_last_update) to confirm which source is updating serial_number.

So the key is not simply creating a Manual Entry rule  make sure it specifically governs serial_number and has the required precedence over Discovery.

This is the ServiceNow-supported way to prevent Discovery from overwriting the manually maintained serial number.

SAIRSM
Tera Contributor

Hi @pr8172510 ,

Thanks for the assistance, I did same as you suggested but it is not working , you can check all my rules under windows servers.

Thank you

Hi @SAIRSM,

The issue is that serial_number is present in two Windows Server Manual Entry rules.

Remove serial_number from the Manual Entry [100] rule and keep it only in the dedicated Serial number → Manual Entry rule.

Set the dedicated rule to a higher priority (e.g., 10), then use Preview Rule to verify the precedence.

After that, manually update the correct serial number and run Discovery again.

SAIRSM
Tera Contributor

Hi @pr8172510 ,

PFA screenshots for your reference, I did the same you mentioned but the serial number is overriding by the discovery.
Thank you