what would you suggest as a best practice or most commonly used for 'SG-SCCM Last Discovered Update date?

[Donna12]

Hello I just upgrade to Service Graph Connector SCCM. For some reason when I put checkmark on 'use last run datetime' for SG-SCCM Last Discovered Update it prompts me for 'SG-SCCM Last Discovered Update'?  I cannot use this unless I manually put in a date.

According to SN support....

"Last run database field " you can choose the datetime field which you want to consider for last run datetime. It's up to you to decide which datetime field you want to choose based on your business need. Servicenow support cannot suggest in this case."

What would you suggest as a best practice or most commonly used for 'SG-SCCM Last Discovered Update date and why?  Thanks kindly

Donna

[Donna12]

here is a screen shot.  this is what the default is.

[Patrick DeCarl1 · Accepted solution]

OOTB should be blank, so uncheck the option. I believe we answer your questions here. 

[#4]

The best practice would be the OOTB values.

As for what the options are and why there isn't a lookup is that it depends on the SQL.

Please read through this article to get a better understanding.

The SQL in a JDBC data source is just a string field, so there isn't a reference to a bunch of different select fields.  Those select fields in the SQL query are what you could choose from.  However they also need to be a date field.

For SG-SCCM Computer Identity the best practice is to use the TimeKey field as mentioned by @Patrick DeCarlo.  This should be a part of the SQL query on the data source.  When you pull the data from SCCM, it will track the most recent value of this field and then put that value in the Last Run Datetime field.  From there it will add that field and value to the where clause programatically to bring in differential records.

[Donna12]

What is the SCCM difference between most recently discovery date and Update date