This could probably be split across multiple posts but they’re all related so I’m posting here as a longer “thread” for these ideas.

Because with Horizon 360 we can remove users ability to create and edit relationships from the C360 so I’m taking another shot at configuring a “Relationships” Tab for the C360 layout. There are two main areas this could really be improved, both are on the admin side and one really impacts the user experience:

Admin Configuration Experience of the Relationship Sections in C360:

• In List View, reordering fields is a nightmare. If I move the last field to the second position, it doesn’t move everything else below it down one slot, it just swaps the two fields. So if I want to move one item up in the list, I have to then reorder every other field below it, each time. This is a step back from how field ordering works in report layouts for show me fields, for example.
• Even the experience between List and Card view is different, as Card view has slots in a layout for fields and List view does not.
• Card View has a preview but List view does not. Why is that? Card view is 2 columns wide and fits a preview, List view is 1 column wide and has no preview.

Configuration Issues that impact end-users:

• There is always a “Default View” under relationship sections that I cannot delete. 

  

  If I only have one relationship type then I don’t need a dedicated secondary view. So, I can make my relationship specific type view match the Default view, but it doesn’t make sense to have both because that is confusing for users. Why would I have two tabs showing the exact same thing? I know it defaults to their preference, but it is unnecessary to display both if I don’t need it.
• Even if I delete the relationship specific one, they both show up on the user side of the C360: 

  

  Even more bizarrely, the card view gives this error: 

  

  but the List view still shows a report. This error is extremely unhelpful and misleading as it indicates there’s a problem with the configuration, not that it is intentionally blank. I guess it is correct in that there is a problem, but it’s a system not a config problem . I even had a ticket a year ago 176920 that spawned a discussion about the detrimental impact that these types of “access” messages have.

• Something that would also be nice to have here, is the ability for admins to create “Relationship Cockpit” Views - What I mean by that, is leveraging the end-user ability to filter their relationships here: 

  

  and merging it with the idea of Admin pre-defined Cockpit Views. End-users likely may not know the correct filters to get what they need anymore than they would in Cockpit, which is why admins are able to help with pre-defined views. I would like to see that here as well and I don’t see a way to do that today.

@anirbandutta not sure if this is across one or more PM’s but if you can help direct it to the appropriate parties I’d appreciate it, as always!