For some connection fields, it would be helpful to see greater information in the connection field than just the name. And for connections that have a large number of values, it would be good to collapse those into a scrollable container of some sort.
An idea for an updated/optional UI for connection fields would be a list view. As an example, we could look at the groups field on a contact. Over time, a contact could be part of numerous groups. It could be helpful to see the status of each group as well as the name, and maybe the last updated/meeting date.
This could be formatted as a row-based list of records instead of the tag/badge style. This could be configured per field definition with the display/custom property (like multi_select has the standard vs button display). Each row could be a link either to the full record page or maybe a quick edit view in a modal. There could also be value in a quick search/filter of the list of connections, but that might be unneeded complexity.
This could be especially useful if we added a record type for activity/interactions that shows activity on a record over time.
Some possible mockups:
For some connection fields, it would be helpful to see greater information in the connection field than just the name. And for connections that have a large number of values, it would be good to collapse those into a scrollable container of some sort.
An idea for an updated/optional UI for connection fields would be a list view. As an example, we could look at the groups field on a contact. Over time, a contact could be part of numerous groups. It could be helpful to see the status of each group as well as the name, and maybe the last updated/meeting date.
This could be formatted as a row-based list of records instead of the tag/badge style. This could be configured per field definition with the display/custom property (like multi_select has the standard vs button display). Each row could be a link either to the full record page or maybe a quick edit view in a modal. There could also be value in a quick search/filter of the list of connections, but that might be unneeded complexity.
This could be especially useful if we added a record type for activity/interactions that shows activity on a record over time.
Some possible mockups: