In Opportunities, I have a simple group, that has several Contact columns that are set to Entity Linked. The field displaying is the Name. But only a few of them are clickable/blue. I checked the database and the CONTACTID for the Entitiy's field is the same for all of them. Any ideas what could be causing this inconsistency?

Do the last name, first name have values in the actual contact? maybe a SecCodeID issue (different value for the contact and the opportunity)?

Last and first name do have values in the CONTACT record. SECCODEID is the same for all.

Looking at the Query Builder I see my 3 Contact joins:

+Contact(sales_consultant_id->contactid) [left]
+Contact(internal_broker_id->contactid) [left]
+Contact(primary_broker_id->contactid) [left] 

Only when an Opportunity has a ContactId in the sales_consultant_id field, do the links show up in the Group/list. And in these cases, the links will all go to the sales_consultant_id Contact record.

Back in the query builder when I open up the Query Layout and edit the columns, I see that all have the same Field Name (Opportunity.Contact.Name) which cannot be edited. The entity is of course Contact but the Property names are different. But the primary_broker_id property is actually called "Contact". Whereas the others are "Consultant", and "IntBroker". Not sure if this has anything do with it.

Ok so after deleting all 3 joins in the Gloabal Join manager, re-creating 2 of the Contact joins, Re-generating the XML Schema, and Restarting IIS, I managed to get the 2 columns to show hyperlinks. However, they are both pointing to the same contact. Still showing the correct names, just not linking to the right contact.

Oh and those columns don't sort 

Do you have Web Relationships for all three of these joins? Not Global Joins, not viewable in the Query Builder, but actual Relationships?

Yes, real web relationships exist. However, after inspecting the relationships, I noticed something odd. 2 of the Contact relationships are 1:M with Opportunity, and the other is M:1. (2 having Contact as the Parent, and 1 having Contact as the Child) Have no idea why they used a M:1 relationship. Functionality is the same for all of them as far as using the properites in code but could this be causing the issue with the Entity links? And if so, what is the best way to go about converting it to a 1:M? Thanks!

I usually delete 'bad' relationships and start over....always from the Parent table.....

Removed all bad relationships, removed the group, removed the global joins, and re-created all and still having the issue. Although I figured out why sorting wasn't working (can't sort on a calculated field). It just doesn't want to use the web relationship property names and instead links all contact columns to whichever contactid is the right-most in the layout.