Painpoints with IH-ETL - do you agree? any feedback you have?

[Suggy]

Issue 1:

We know that IH-ETL uses IRE, but its actually something like we are configuring/mapping the CI identifiers as part of the Attribute mapping step in CMDB integration studio.

ie say for computer, OOB the CI identifiers are like this

and this is what we map in the in studio. All the above identifiers are presented in the mapping step.

Suppose if you have 10 ETLs, you have to edit all of them in case you modify the CI identifiers. Suppose you had used Data source/transform map, you just call the IRE API and any changes done to CI identifiers will not be impacted, but in IHETL you need to update all those 10 ETLs

Issue 2- 

In Data source/transform map, you have the 'Choice action' to easily create/ignore/reject but the same is not avaialble in IH-ETL. You have to code it to do it.

Issue 3-

In Data source/Transform map, once the data is transformed you can see how many records got  inserted, updated, ignore etc.

TotalInsertsUpdatesProcessedIgnoredSkippedErrors  

The same does not work for IH-ETL.

[Suggy]

.

[Siyou Li]

For issue 1 and 2, I need more details regarding the feature parity you referred to between IH-ETL and transform map. Could you please provide an example of what you are using in transform map and the problem scenario you are trying to solve.

For issue 3, IH-ETL final preview page provides information regarding what records are inserted/updated. And it also shows the activity and error logs.

Details in our IH-ETL community article:

https://www.servicenow.com/community/cmdb-articles/ih-etl-guided-setup-step-6-test-and-rollback-inte...

https://www.servicenow.com/community/cmdb-articles/how-to-use-integrationhub-etl/ta-p/2300472