Most Recent Discovery date behaviour

[stevejarman]

Hi all - I'm looking for a definitive answer on whether or not the Most Recent Discovery date on a CI should update EVERY time Discovery sees the CI, regardless of whether or not anything has changed? OR, does it only update the Most Recent Discovery date on a CI if/when it discovers changes to it? I feel like I'm seeing mixed results sometimes...

I've also noticed that an update to Most Recent Discovery field does NOT update the Updated (sys_updated_on) field. That's correct? It seems like changes to Most Recent Discovery field are exempt somehow from "dirtying" the record.

[Ashutosh Munot1]

Hi,

So this field will be updated whenever you discovery schedule or you discover the CI.

https://community.servicenow.com/community?id=community_question&sys_id=b4330be1dbd8dbc01dcaf3231f96...

Thanks,
Ashutosh

[stevejarman]

This isn't a very clear answer - are you saying when the Discovery Schedule runs or you discover the CI? The thread you've linked to also gives a mixed answer indicating that it is different depending on the class of CI.

This is why I'd like to see a "definitive" answer on this from someone who knows exactly how it works. This is a very important field - it should have clear rules that are documented somewhere, but appears to be another ServiceNow mystery...

[Ashutosh Munot1]

Hi,

Yes this is indeed important because for calculating node value this is used.

@doug.schulze  Can you comment on this.

Thanks,
Ashutosh

[doug_schulze]

Yes, on every 'identification' of a discovered record we set the most recent discovery date even if nothing changes on that ci. And yes it does not directly reflect in the updated field in all cases. What those cases are I do not have an answer to. but very confident in the most recent discovery.  What challenges are you facing?