Junction table (imperfect) workaround
Since I have used Polymorphic models for decades, I was unable to wait, so I have many junction/join tables (similar to helper databases described here) in the form of subject relation fields and object relation fields, enabling the following:
- To connect a subject entity to any object entity, within the same field, i.e. the junction table relation field on the subject entity.
- To keep polymorphic relations modelled in the same way, to allow migration to the feature when it is finally launched.
- To add Formula fields on the junction table to roll-up a field from across the different objects, to then be used by the Subject entity.
- To have multiple subjects sharing the junction table.
- This has the added benefit of allowing relationship attributes.
Accessing fields from the junction table
With the possibility to add the fields of a relation to the UI without the need for lookups, this junction table approach, becomes slightly less cumbersome.
Example
I had Claude whip up a quick diagram below with the example junction table Workables, meaning a Taskwould have a Workables relation field, but would mostly use things such as Workables.Sum([Rollup of some data from across objects, e.g. effort, cost, etc.])
