Avoid insert in CMDB from SCCM using Integrationhub ETL or Robust transform map
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2022 03:54 AM
Do we have an option to ignore insertion of records in CMDB using Integrationhub ETL or Robust Transform Map.
We are replacing SCCM integration with SCCM graph connector and will be using RTE to import data. But as per our current configurations SCCM allows only update on existing records we are not allowing any insertion of CI from sccm and for that we are ignoring in transform script if action is insert.
How can we replicate same thing in Robust Transform Map? Is there any way to ignore insert from RTE and only update should happen.
Thanks,
Anjali
- Labels:
-
Service Graph Connector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2022 05:40 AM
Yes, although it is not in the ETL or Robust Transform Map. You want to handle this on the IRE side as the output of the ETL and Robust Transform Map is just an IRE payload. You will not know if a CI exists or not at that time, so you need to handle it within the IRE.
In the IRE you can define a data source rule. This will allow to to specify what classes certain sources are allowed to insert data into.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2022 05:59 AM
Thanks for your reply!! It helps, one more add on to this, in our current configuration if action is insert then we are gliding a separate table in onbefore transform script and creating ticket for those source records that sccm trying to insert.
Is this also achievable in RTE?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2022 09:52 AM
No, it isn't achievable through RTE. As mentioned the end result of the RTE is an IRE payload. The IRE is then responsible for determining if it is an insert or update.
In that situation you may want to create a business rule that runs on before insert that will abort the transaction if the discovery source is SG-SCCM. In that business rule you could create your tickets as necessary.