using the native “expand row” feature, must all rows in a view share the same layout?
I have views where this makes sense and is fine, but if I want to have “overview” tables for people to look things up, I run into issues when they click for more details and are shown the wrong layout (and thus too few or extraneous columns).
For example, I have a master table that lists 200+ countries in the world. Each country is a row, with about 30+ columns containing more information. some of these columns determine which other columns are relevant. But if I want people to be able to view the full list of countries and be able to click on one to expand for more details, I need the details to be displayed in the appropriate layouts.
is the only workaround to create canvas templates for each layout that display the columns desired and then configure the canvas column with a formula? for example, instead of a table listing all countries with 30 columns, I would have a table with 1 canvas column and a formula determining how that canvas column displays some of the 30 columns?
Here is how I go about this if I understand your question:
I create my own expand button where I use a switchif to decide which view will open. I keep a different table for each view I want and have the switch if open the desired view.
If you are referring to the grey expand row that appears to the left of a row when hovering over a row, this cannot work in the same way as the manual button that I made. That native button will only expand the view that the table is set to, and there is no way to disable the view of it.
I will say, however, once you and the people using the doc get used to using the blue button (I recommend coloring it) they will automatically use that button versus the native expand. It’s just more intuitive and user friendly.
If you already had them using the native button then it will take a little bit of time to get used to.