foreign Ando I'm a senior technical consultant at glyfast today I'd like to cover a new feature in the Utah release the identification and Reconciliation engine ire has been updated to allow the processing of non-cmb tables like the location department and user tables these tables are foundational data elements of the common service data model or csdm framework the ire serves to identify and reconcile data from multiple sources preserving the data Integrity of both the seem to be and now newly supported non-cmdb tables let's walk through a quick demo on how we can leverage the re to import data from an external Source in this example we'll be importing phone numbers from a spreadsheet into the location table let's get started by first creating a new identification rule navigate to the CI identifiers menu next we'll create a new record we'll enter location as the name for this new record and select location from the applies to list next we'll configure some identifier entries enter location for the search on table field we'll select name and parent as the attributes and leave the priority at 100. next we'll create a second identifier entry we'll select location again as a search on table for the attributes we'll select name and State we'll set the priority to 200 and submit the identifier rule for locations is now set to use our newly created identifier and to Leverage The ire we'll Now navigate to the Integrations Hub ETL to create a new transformation map using the guided walkthrough we'll click on the first step to import our data and to provide a name for the transformation we'll populate a transformation map name a discovery source and a data source click the new button to create a new data source populate both the name fields and select Excel for the format we'll use the attachment icon to upload our Excel spreadsheet hit submit to save our new data source now we can see the record and Mark this step as complete next we can preview the data we imported and add any Transformations if required as you can see in the preview of our data not all records have parent values this is where we can Leverage The ire and the CI identifiers we created earlier since the parent value is just a name we'll need to do a lookup to get the sysid of the parent record as you can see the new parent sysid column has been added we can now Mark this step as complete we can now move on to mapping our source data to our Target location first we'll add a class in this case we'll select the location table we can now go through the process of mapping each individual column since our use case for this demo was to import phone numbers We'll add the phone number attribute and map that as well we can now Mark this step as complete since the ire does not support relationships with non-sumdb tables we can mark this task as complete the final step now is to test and run our integration as you can see the phone numbers from our Excel workbook have been successfully imported this concludes the demo of the new updates to the Irv in the Utah release thanks for watching [Music] thank you [Music] foreign [Music]