Import assets with multiple relations of same name
Hello everyone,
we’re having two relations, both valid for Physical Data Dictionary.
One is the out-of-the-box “Column is part of Table” and one is the (from RDBMS side missing) “Foreign Key is part of Table”.
Now a problem appears: if you want to import from Excel or csv the name for Automap must be “is part of Table > Full Name” etc. in both cases. Automap only maps to the latter relation.
Is there any option to exactly declare, which relation is meant? I already tried “Column is part of Table > Full Name” but without success.
Thanks a lot, Manfred
manfredsorg
Posted 4 years ago · Edited 1 year ago·Last reply 4 years ago
6 comments
markthacker
·4 years ago · EditedHi @manfred.sorg I feel your pain and the duplicate role problems, can create a lot of frustration. Typing the Tail asset type speeds the manual process mapping up but selecting can always result in an error. If it is feasible manipulate your import sheet to include just one of the (duplicate roles) relation types one at a time, I guess we call that working within a constraint
manfredsorg
OP4 years ago · EditedHi Mark, unfortunately this is not a solution. Collibra decides on itself which relation to choose - which is worse than not assigning. The clever partial solution to decide based on left side (source asset type) is not implemented. In my case it assigned the relation based on “Foreign Key” to “Column” entries.
Petr Horsky
·4 years ago · EditedHi @manfred.sorg ,
I came across the same issue and there is probably no way other than mentioned above. You might also change the name of the role (or co-role) of one of the conflicting rel. types however this is probably something you don’t want to do.
This behavior is unfortunate. A convention to fully specify the required relation type would be useful here.
Petr
akashmittal
·4 years ago · EditedHi @manfred.sorg ,
If you don’t do manual mapping, Collibra will get confused between the two relations as they both using the same role/co role names and will build the relation with the latter relationship column.
IMO, You have 2 options, experts in this community might add any other option I am missing:
Regards,
Akash
Former User
·4 years ago · EditedHello Manfred,
Not sure if I understood the problem and if you know that you can manually point the column from import file when you do mapping so the headers don’t need to match. Please see the picture.
manfredsorg
OP4 years ago · EditedHi @tomektomiczek.gmail.com ,
thank you, but I’d like to avoid manual matching (test data for a training I’ll have to import regularly).
Automap won’t work if the verb and the right side of a relation are duplicates.
My question is whether there’s an idea to circumvent this.
Thanks a lot, Manfred