I’ve stumbled upon a pretty serious limitation - at least for the usability of my particular doc - that I hope can/will be resolved soon.
I’m a big fan of the expand row/row layout feature in Coda. Here’s the default layout of a master table:
Now what if we wanted to make one or multiple views of the master table with their own row layouts? Good news, we can!
Now what if - depending on particular conditions/circumstances - we tell a button to add a row to a particular view of the table, so that the user gets to see the most relevant row layout for that particular situation? E.g. [View of Table].addRow().Activate(). The good news: you can tell a button to do that; bad news: it ignores your request and ALWAYS redirects to the master table.
Has anyone else noticed this and/or found a way to work around this? I’m keen to get some clarification on this.
PS. You might wonder ‘why not just make multiple master tables then?’ That would indeed solve the redirection issue, but I have a master table that cannot be clearly cut up into smaller tables: there are overlapping combinations of columns I want the user to fill in, depending on certain conditions.