The only way I could work out how to do this, was to -
User specific column in the users table
Write to that column when one of the headings is clicked
Add a relation from that column, back to the data you want to show
Add a lookup field for each field you want to show
Then add a custom collection with two columns - list on one side (for the headings) - then a field view (or similar) on the other side pickup up the data from the lookup fields created above.
Is that really the way to do it? Seems very long winded and requiring a lot of columns to me, so want to check before I go too far.
You can simplify that by making the source of the top level screen the Contacts table, and then use the value that’s set in your user profile row as a filter (at the screen level). That way you don’t need the relation or all the lookups. Just add a fields component in the right hand column, and the filtering will ensure you’re using data from the correct row.
It’s because the filter is being applied to the screen, rather than the collection.
When you first create the screen, it’s attached to the first row of the Contacts table by default.
But then once you add the filter by selected ContactID, you’re essentially navigating up and down the table as you select each Contact.
It’s a neat technique, and one that had never occurred to me until I saw your post yesterday. I was actually inspired to use it in an App that I’m working on at the moment
I took it a step further and added a marker to indicate the currently selected record:
