How to use single transform map to transform data on different tables ?

[Siddhesh Gawade]

Hello,

I am using following approch to avoid creation of many transform maps for different lower-level tables

Create a field map of "Class" field (sys_class_name) where I can define the backend table name of each class, e.g.: 'cmdb_ci_esx_server' or 'cmdb_ci_server' and this should present in source file (csv or excel). Using the above approach I  can build  transform on the "cmdb_ci" table instead of individual class tables.

However, with that approach, product models are getting duplicated. . also I don't want to relying on the higher level (cmdb_ci) but on individual lower-level tables e.g. cmdb_ci_esx_server, or cmdb_ci_mfp_printer.

If anyone could find a solution so I do not have to create transform map for each lower level table.

Regards,

Siddhesh

[Allen Andreas]

Hi,

Great suggestion. Forgot about this (have never actually used it, yet).

This seems like a possible use case. Curious how it would look for this situation.

Thanks again for bringing it up!

-Allen

[SELECT Username]

IntegrationHub ETL!

https://www.youtube.com/watch?v=YvsCY0M7JLw&t

In a legacy transform, if you're having trouble with model information, it's probably because you're trying to map directly with an incorrect reference field selected.  The better way is to use makeAndModelJS to reconcile models rather than mapping them manually.  If you're integrating at the cmdb_ci level, you may still have issues if there are models in different model categories.

Transforming to ESX server, I'd strongly recommend Discovery over rolling your own integration:

https://docs.servicenow.com/en-US/bundle/sandiego-it-operations-management/page/product/discovery/reference/r_DiscoverESXServers.html