Skip to main content

We should ideally be given the choice to have a second link field populated when using links to records in same table. For instance I would need a children field to be automatically populated when parents are added (and vice-versa). All workarounds suggested by support team (via automations or via a secondary relationship table) have limitations.

A same-table parent/child linked field feature is absolutely needed - probably my number one required feature at this point in time.


Reply