We have many tables to join that all have complex keys. Is there a way to have Yellowfin detect the foreign keys? Matching by fieldname doesn't work very well in our case. It picks up too many fields. I know they can be removed, but it becomes cumbersome for the number of joins we require, and the number of views we need to create.
and there is no other way to change this process of YF matching by datatype.
pardon me, it just occurred to me that you were most probably referring to the Detect Joins feature, in which case the answer is "no", there isn't a way to have YF detect the foreign keys, it only matches by fieldname and does not look at any underlying join logic built into your database.
So perhaps in your situation it would be better to choose the foreign key manually rather than use the Detect Joins feature.
I'm just going through my work list and checking up on things and I noticed that this case has been hanging around for a month so I'm asking whether it can be closed now?
That is fine. The only thing I would wonder is if this should or can become an idea for possible future enhancements.
Subject: New Comment in "Joins in a view: How can I have it detect the foreign keys instead of matching by field name?"