How to use IH-ETL Associated Classes to populate Parent field on Location

mcarter89
Tera Contributor

I need to port location data from our legacy CMDB. Because I want to create the ServiceNow recommended hierarchical structure for the location records, and don’t have the concept of ‘parent’ records in my source data, I am sticking with the IH-ETL rather than transform maps, at least for now. I might have found an issue that will force me to change something though.

mcarter89_0-1721681378822.png

 

I watched a ServiceNow youtube (https://www.youtube.com/watch?v=ZRZxRSOvp4k&t=1483s) that is just pulling in city and state data. It uses the above screen to set up associations that allow for the parent fields to be automatically populated. Meaning, when you find a record that has been mapped as a city record, for example, you can set up an association with the state records, so that it will know the parent of a city record should be state records.

 

In my case, I am wanting that type of relationship that steps from the granular Site to City to State to Country to Region. But it seems this page will only allow for two of these classes to be associated with each other. If I connect Site to City, for example, then I don’t have the option to connect City to anything. I can then go connect State to Country, but then I have the same problem if I want to then connect Country to Region.

mcarter89_1-1721681378826.png

 

Note how the “Add Associated Class” tabs have disappeared on “Country” and “City” records. Is this possible? Or do I need to build a script somewhere to achieve this?

2 REPLIES 2

Nico Kampf
Tera Expert

Hi, 
have you found a solution for this?
I am experiencing the same issue.

 

Regards,

Nico

mcarter89
Tera Contributor

Hello! Thanks for the opportunity to follow up on this. Unfortunately I didn't find a solution to this. It turned out that because the data I was trying to populate was more of a one time load, I moved away from using IH-ETL and instead used a series of transform maps on each level in the location hierarchy. That ended up working fine and any updates since then have been minimal, so we decided that is enough for our needs.