Relationship properties

Ideas & Features
30

I think that is one way to view this.

At the moment I can model the data in as many databases as needed and specify the needed relationships to build just about any data model. But the UI has limitations in how it can be configured.

The current setup has its disadvantages. For example:

  1. The number of databases that are needed is increased, which increases complexity [Not a huge deal]
  2. Duplicate work for creating lookup fields to the related databases [Also not a huge deal]
  3. Lookup fields are not editable, so you are not able to use lookup fields if the field needs to be edited [ Editable Lookup Fields ]
  4. For editable fields you need to create automations that update the fields on all other entities [This is a lot of work]
  5. Navigation is limited. Depending on the relationship structure, clicking on an relationship within an entity does not always take you to desired entity.
  6. You could circumvent the navigation issue by allowing for fields to display different data depending on context. [ Formula fields that are filtered by the context they're viewed in ]

If you could do 3 and 6, then relationship properties might not be needed at all.

2 Likes