Relationship properties

[Sev]

Thanks for clarifying your scenario. I have recreated it in a test space to make sure I was not missing something. Below, I am going to go through each issue to see if I can address them.

I will base my answers on accessing Related Contacts on a given Account’s entity view, but everything applies in the reverse direction, too.

@danielbmarsh

I never want to open the Role

@danielbmarsh

and I click on a Role I want it to open the associated Account

@danielbmarsh

When I click on a Role I want it to open the Contact (not the Role).

But, clicking on a role should never open an associated account, since they are different types of entities. What if you want to edit the role, for example, the period, the actual type of role, or even the contact assigned to the role? That should be possible to do, and is, as shown in the video.

@danielbmarsh

If I want to display the email and phone number of the Contact, I can do so, but it either takes uneditable lookup fields or new duplicated fields and automation rules to make work.

I do understand that in most cases, you may need to quickly modify the fields of either end of this many-to-many relationship, i.e. an account’s fields when on a contact view, or a contact’s fields when an account view.

This is possible as shown in the video below, as long as you do two things:

1. Establish the Contact-Account relationship by simply adding a lookup field on Contacts to look up Accounts through Roles.
2. This enables you to set Contacts as a level in the table views of the Roles Relation Field on Accounts, and it correctly shows only Contacts that are related to to the Account being viewed.

This is how in the video I am able to edit Contact Names, Emails and Phone numbers right from within the Roles Relation Field on Accounts.

But there are a few problems, which make me think my ability to edit related Contacts on the Account Entity View, is more of an unexpected, accidental side-effect, than a feature.

1. It only is possible if the corresponding lookup field is set up on Contacts, even though we do not use the lookup field on the Accounts table, and it does not establish a new relation.
2. If we do not add the corresponding lookup field on Contacts, then All Contacts, regardless of relation to the current Account, show up in the Roles Relation field on the Account Entity View.
3. When adding a contact in that view (presumably because it is NOT nested-under /connected-to a Role, it results in this error: Cannot add collection items to readonly "Testdb/Roles Accounts" *(this is the lookup field we had set up)* field for "Testdb/Contacts" database.

@Sev

• to change the UI component for *-to-one relation fields to the same as the “relation list view” currently used for entity-returning formula and lookup fields, since it allows at least the addition of fields to the UI.

5. As I had mentioned earlier, when a relationship is many-to-one, such as the relationship between Role and Contacts, then we cannot set Contacts as the sub-level of Role in the table view. We can still set Contacts as the top-level entity, which is what I have done in the video, but I would rather be able to edit a Contact nested under its Role, rather than directly like I show in the video.

@danielbmarsh

We also have another issue of when I am on the account I want to create/ add a new contact with a title. I am essentially required to create a role and include all the contact fields that I want to show on the role.

In reality you should just create a new role, and in its Contact relation field, you create a new Contact. Once created you can edit that Contact in the list above shown in the video. There is no need to expose the Contacts Fields on the Role itself. Though I may be missing something here in which your use case differs. Sorry if that is the case.