ServiceNow Intune most recent discovery not correct
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2023 06:20 AM
We are using Service Graph Connector Microsoft Intune application.
We have configured it and its importing assets correctly however under the "Most Recent Discovery" field, the date and time is not correct (its not matching what its supposed to be transform mapped to).
The field Most Recent Discovery is mapped to "lastsyncdatetime" under IntegrationHub ETL , when I go into IntegrationHub ETL and do Test and rollback Integration results, I can see lastsyncdatetime correct however when the scheduled import runs the most recent discovery field is showing something different , it is showing a date and time nearly identical to the "Updated" field. not the last sync date time from Intune.
See below screenshots
Screenshot from IntegrationHub ETL Transform Map to CMDB configuration
Transform configuration
When viewing the CMDB Table , the most recent discovery is is showing different values
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2023 11:02 AM
Hi,
Pls check following entries.
1. Check the ServiceNow Instance (Server) timeline
2. Check the User Preference & User profile timeline.
3. Compare the Intune system and ServiceNow Instance timezone.
Suresh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2023 06:41 AM
Everything is set to GMT timezone but issue still persists
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2024 10:09 AM
Hi Ahmet, I am wondering if you tracked down what was causing this issue? I am also seeing the behavior in my SG-Intune integration. The ETL mappings look correct. I'm speculating there is something else kicked off when the integration runs that does this update but having trouble tracking it down.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2024 05:27 AM
Hiya, unfortunately didn't fix the issue but we got a workaround in place which has helped it working!
We found that the issue is due to that specific field which its mapped to out of box causing the timing issue.
Basically, we created a new custom field and called is like LastSynced , mapped it to this field and then the numbers started coming in much better. Try that!