I have a drop-down select menu that affects a filter in different tables on different pages.
Currently there’s one page on which I can select the filter and all other pages have a formula, showing the value of that selection.
Ideally I’d like to be able to have a drop-down select on every page that is synced. So when I change a value, it’ll affect the selection on every other page and vice versa.
Specifically I’ve got a page for each Tasks, Notes, Meetings, ect
All those elements on the pages have the attribute >project< which is being used as a filter for the views on the pages.
I want to be able to switch between projects, without going back to the “master-select” which is currently affecting every other page.
Hey @Konrad_Mertner , first of all, that looks like a cool doc design, would be cool if you share more of it for others as inspiration.
Regarding your question:
There is currently no native way I know to sync two “real” canvas select fields.
There is an easy workaround, but has small implications in layout, and big implications depending on who is using the doc!
Let’s assume you are the only user:
Create a new table with a name colum and a select column. In the name column enter “Auswahl Projekt”, in the projekt column make it a select as you have it now – but in a column instead of a canvas control.
Now make a view of the table everywhere you need the select and in the table settings deactivate basically everythin like table name, column headers etc., and hide the name column. Now all that is left is the select (with some spacing differnt than you have it now though)
Everywhere you want to use the select, reference the row with the @ sign, like @Project Auswahl.[Select Column]
This way you have one select with different views in sync across pages.
Problem: Like described above, it is not “Collaborative” and not “Personal”.
To make it personal, you need a row per user in that table, and then filter the table everytime to only show the users select – and also everywhere you reference it, you have to filter the table by the user as again.
I’ll give it a shot, tho the non private nature of that solution might be a show stopper and I’m not sure if I want to create a row for every user. On the other hand, that row might also be part of a user-database I’m going to have anyway…
I’m sharing the doc, once I stripped away all sensitive data, thanks for appreciating my design
Update: The limited layout-options by being a table-view are a show stopper for us
Yes, for most complex docs I build, I have a user db table where I manage permissions, user groups, and these kind of selects.
But the layout implications are also what I hate about it, so most of the time I work with a list if buttons instead. It is one button per select item that when pressed updates the (not visible) select list.
Its fully dynamic with the use of button formulas. So everytime a new client is added to the Client DB table, a new button shows up here – but only for the employees assigned to that client etc.
It also has layout issues, especially if there are e.g. 100 clientes
OK, I found a good solution to my problem. Since sharing is caring, here’s my approach:
Also Buttons! Kinda similar to your implementation
I basically have multiple selects that power a value that is being inserted into a master select on a hidden page as well as any other individual selects.
So you basically chose a project and “open” it with the button, which inserts that selected value into that master-select as well as the select-menus on every other page.
That gives the illusion, that those selects are the same
as a plus: Having a stop gap in chosing a project is quite handy when presenting infront of an audience, not supposed to see information to a project they’re not supposed to see.
