- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello all. I am setting up the Service Graph Connector for Intune and have a requirement to bring in the Assigned To aka UserName ONLY for the Handheld Computing Devices.
OOB, it's bringing in & setting the Assigned To for all things in the Computer class. We don't want that & I'm struggling to figure out how to limit that to just the Handheld Computing Device class.
In IntegrationHub ETL, I've tried editing the SG-Intune Device Reports mapping under Select CMDB Classes to Map Source Data multiple ways without success. I've also tried editing the Robust Transform Engine but hate to get that deep in the weeds if I can filter via IntegrationHub ETL.
Any suggestions or help is appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
As far as I know, there is no option to set this through the connector itself. However, this is a great use-case for reconciliation rules within the CMDB. For all hardware classes you can create a reconciliation rule where the SG-Intune is NOT allowed to override/edit the assignet_to field. Then, for handhelds, you can setup a reconciliation rule where SG-Intune will be able to override that field.
This won't limit the connector. It won't need customization. But it will prevent Intune from writing into the assigned_to field. The only thing you will need to check is related to empty fields. In case there is no value in that field, you will need to decide if the info from Intune is "good enough" or not. Depending on that decision, you should allow or prevent Intune from overriding empty field values as well.
Hope this helps,
Regards
Fabian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
As far as I know, there is no option to set this through the connector itself. However, this is a great use-case for reconciliation rules within the CMDB. For all hardware classes you can create a reconciliation rule where the SG-Intune is NOT allowed to override/edit the assignet_to field. Then, for handhelds, you can setup a reconciliation rule where SG-Intune will be able to override that field.
This won't limit the connector. It won't need customization. But it will prevent Intune from writing into the assigned_to field. The only thing you will need to check is related to empty fields. In case there is no value in that field, you will need to decide if the info from Intune is "good enough" or not. Depending on that decision, you should allow or prevent Intune from overriding empty field values as well.
Hope this helps,
Regards
Fabian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
THIS! Fabian, I knew there was something I was missing. Thank you! Perfectly simple solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Thanks. If you want to be more granular and have more insights on how to harmonize your source integrations, take a look at the multisource/CMDB360 plugin from ServiceNow. It gives you more granular control and even dynamic recon. rules for very specific cases.
Happy i could help 🙂
