Coalesce on a reference table item

[scott_moen]

I am attempting to import a big list of relationships into cmdb_rel_ci using an Import Set. When I define my Transform Map I create a relationship between a hostname in the import table and the target "child" which is a reference table. I have experimented in the field map settings with setting the referenced value field name (and leaving it blank) and also setting the choice action to "reject" but regardless of the combination of these settings, when I run the transform I end up with a new record inserted.

I have experimented enough with coalesce on table elements so I am pretty comfortable with making it work in that context. Is it possible to coalesce on a reference table item as described or do I need to add a custom script to make this work?

[scott_moen]

To close this out -

We discovered that we had some duplicate data in our CMDB: two entries with the same name but under different tables (so not obvious). Since the 'coalesce' function is essentially undefined for cases where the constraint is not unique, the system simply picks one (child) and adds in a new record. I appreciate all the help from here - this one was a challenge to track down.

[tanya71]

Does anyone steps to create a custom field in cmdb_ci 's extended tables like cmdb_ci_win_server. what are the steps to create a custom field and set its property   as coalesce in cmdb_ci_win_server, would prefer to have option to update or insert a record based on the coalesce property of that custom field during an import

[Community Alums]

Using a custom field to coalesce is no different than an OOB field. You just need to make sure that you've got the field available when you create/update the transform map.   As to the insert/update choice based on coalesce value, I'm not sure that would work. You can choose to insert or update a row based on a value but I'm not sure I would reconcile that.