In your scenario the junction table works fine as the table displayed on the entity. Although no field that is a lookup field on the junction table is editable, as that feature doesn’t exist.
In some scenarios it’s not quite that simple. I’ll give one example. 3 Databases (DB) Accounts, Contacts, Roles (a junction table with 3 editable fields: Account, Contact, Title, & other lookup fields).
- Contacts and Accounts is many to many
- Contacts and Roles is many to one
- Accounts and Roles is many to one
In this scenario we have a navigation issue. I never want to open the Role. When I am on the Contact and I click on a Role I want it to open the associated Account. And when I am on the Account the Roles relation shows a directory of Contacts associated with the account. When I click on a Role I want it to open the Contact (not the Role).
We also have the editable lookup fields issue. 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. At least this issue has a work around.
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.
Having some sort of context based formulas / fields would allow us to to use the Contacts instead of the Roles on the Account and would alleviate this issue in part.
Again I think you are spot on with this being a UI limitation rather than an issue on the DB side.