Am I missing something, or is it impossible to disable this option to ‘show hidden columns’ in a subtable? I.e. a table on a detail layout when you open a table row. I know it’s possible on a normal view of a table, which is very useful, but when it comes to a view of a table in a detail view, is it impossible?
I have a lovely new, functional coda doc set up where my group members can RSVP per gig on a form. The detail view per gig very neatly allows a subtable for people to see who else is available or not. Unfortunately it seems possible for any viewer to click through and show all other columns on the form submission, making private comment column on the form meaningless, or any other related info like email address not as private as I’d like.
Am I missing something?
Hi David,
A detail view is displayed via a layout. In the setting up of the layout, you have the option to disable hidden columns:
And you get to the layout as follows:
Thank you for your reply, Piet. I think I used the wrong terminology when I said detail view. Maybe I should have said ‘open row’ view. I’ve embedded a stripped back copy of the doc so you can see what I mean. I am talking about the subtables on the layout you get when you press ‘gig info’ button on the cards. Anyone can then see all related info for each row in the people table and each row in the signups table. Am I right you can’t stop these columns being shown from there?
Link: https://coda.io/d/_d8JyeRAeNUP/Upcoming-Gigs_sumM5
<iframe src="https://coda.io/embed/8JyeRAeNUP/_sumM5?viewMode=embedplay" width=900 height=500 style="max-width: 100%;" allow="fullscreen"></iframe>
Hi David
What you see is governed by the viewOrLayout parameter - Change the layout you use there to look the way you want it.
The add new meeting button does a similar thing:
P
1 Like
That’s a great doc! Thank you for your help.
Ok so I already understood most of the idea of changing layouts as you describe, although I could definitely make more use of the features of the openrow formula. What I’ve done is add a ‘totext’ formula column in the Signups table to turn name relations into text. This means there’s that layer of separation between the people table (with more sensitive info like emails and phone numbers) and the signups table, which I want to be mostly visible to all. Then I can hide all other columns as you suggest and there’s no way to drill through related data to find other peoples’ emails…
I think I’m right in saying that anyway! Does this sound sensible?
