Hello,
I have several tables with slices with all or part of the data depending on the establishments and users of each establishment.
However, when a slice with a limited number of data is in a view and users want to filter the view, users have in the filtering options all the values of the table and not only that of the slice.
How to avoid this? This damages the experience and is a major security problem if you have personal information that should not be accessible in other establishments
Thank you for helping me !
I believe the default filter includes all the options that have been saved in the backend table for that view.
So for example, if there is a [Status] column and it has three values, "Open", "Complete" and "Canceled" saved in the backend table, then the filter will present all those three options irrespective of if the slice contains records with only status as 'Open"
There are some other limitations of the default filter such as the app creator cannot set the order of the options, so if the 'Status] column is saved in order "Complete", "Open", "Canceled" at the backend , the filter will show options in that order.
If the order of the saved records is changed, the options in the filter also change as shown below
As an alternative, depending on your requirement, you may wish to create a filter wherein slice itself is created based on selected option. But it could be some additional work and feasibility will depend on your exact requirement. Please take a look at the below sample app to get a feel of slice based on user selections.
Slice based on user input - AppSheet from the help article Get started by using the sample apps - AppSheet Help
The above app is a simple representation of the concept and will work for only one user at a time. For multiuser environment, you would need a users table with one record for each user that store the selections of each app user.
User | Count |
---|---|
18 | |
10 | |
8 | |
6 | |
5 |