Hi Griff,
I am glad it helped.
Hi Wahaj,
I have been thinking further about what you wrote in earlier messages and finally think I follow you.
At your suggestion, I went back to look for multiple instances of Tamarac fields with data type lookup and target record type Connection Role, and indeed they only appear on Connection records. (So my understanding about that was wrong before.) Here’s one example:
I believe I now understand what you have been trying to tell me: the system design of Dynamics 365/Power Apps is that the only entity that a field with data type Lookup and target record type = Connection Role is allowed is a Connection.
I am going to give up trying to create the ROI Connection Role field as a lookup and make it a single line of text instead and have downstream workflow steps or human users install the proper type of Role(To) value on the connection instance.
Thanks very much for your patience and persistence! Although it’s not a happy answer, thanks to you I now have the answer.
Best regards,
Griff
Hi Griff,
I am not sure how Tamarac created a lookup for Connection Role (or Connection entity), which is not allowed by design in the Dynamics 365 CE platform. PLease note, it is not a security issue.
It might be a custom page or a web resource.
If you can share the screenshot of that lookup/page, I might able to understand it better.
Thank you,
Wahaj
Wahaj,
Thanks again for hanging in with me trying to understand the problem. We aren’t on the same page yet though. Maybe this diagram will help:
Make sense? I’m still mystified (other than some security thing) why I would not be allowed to create a custom field using the existing Connection Role lookup views to provide the user values to select from.
Griff
Hi Griff,
As per system design, you cannot create relationships with Connection Role entity:
You need to re-look at the requirement and design it differently.
As far as I understood, you need to add a lookup on the Contact entity, and the user should able to select a role for it (same values as of connection role).
In that case, in my opinion, you have following options:
I prefer using a custom entity, I understand it might not be an ideal solution, but this is the only workaround unless you revisit your requirement.
Wahaj,
Thanks for following up on this.
Griff
Hi,
Thank you for the explanation.
Actually, it is not a permission problem. You cannot create a lookup for the connection entity (this is by design).
The only way is to create a connection with out-of-the-box functionality.
You can connect a contact with another contact.
Just change the view while adding a connection:
Hi Wahaj,
Thank you very much for your reply. I probably could have clarified my scenario better.
• I am not trying to enable connections for an entity, I am trying to supply my app user with a list of existing Connection Roles so they can describe a connection instance that needs to be created in the application.
• We already have enabled connections between Contacts. The scenario I’m addressing is where a new contact-to-contact connection instance needs to be created, and we ask the user to specify the Role(To) value. The possible Role(To) values are already defined as Connection Role records (e.g. Attorney, CPA, Insurance Agent, etc.) in the solution.
• I am building a custom form with a field (Professional Contact Role) that I want to define as Data Type Lookup, with Target Record Type “Connection Role.”
• There is a Connection Role Lookup View component in the solution.
• My problem is that there is no entry for Connection Role in the Target Record Type drop-down menu in the field editor when I go to define my Professional Contact Role field.
• I’m thinking it may be something to do with security roles, but cannot find where I would manage that.
Please correct me if I have misunderstood your answer.
Thank you very much,
Griff
Hi,
Thank you for your query.
Connections are enabled on the entity (table) level. You cannot create a lookup for Connections (and there is no need for it).
You can enable connections for your entity using the following steps:
Configure connection roles - Power Apps | Microsoft Docs
If you are using classic customization interface, follow these steps:
Once, connections are enabled, you should see connections in the related tab.
Hi Nya,
Tamarac is a layer on Dynamics. I believe the Connection Role entity (and related Views, Lookups and N:1 Relationships are defined in Dynamics. That's why I posed the question in this forum.
Griff
Adis
136
Super User 2025 Season 1
Sohail Ahmed
81
Jonas "Jones" Melgaard
77
Super User 2025 Season 1