Using Shared field in Multi Select
Want to confirm if the behavior I am seeing is repeatable by others and also if others believe this is a bug I have roles set up in app which limit the view and modify access to records in Table A ...
Forum Discussion
Hi Scott,
What you are seeing would be the expected behavior when you use the option in the field properties to base a fields choices on values from another field. Since that is being set on the field by an Admin it isn't applying the usual view permissions used on records and instead simply pulls over the list of options available and inputs it into the field. This means that your users would see all choices instead of just choices that they have permissions to since all those choices just get loaded into the field.
Typically when a builder is looking to maintain that control we recommend using a join table between the two tables to mimic a multi select field with an editable embedded report on the table B where you are making the choices pulled from the join table. This way you can have users select more then one choice and still control what records they are able to see by the permissions you set in Table A. I hope that suggestion is helpful Scott.
------------------------------
Evan Martinez
Community Marketing Manager
Quick Base
------------------------------
What you are seeing would be the expected behavior when you use the option in the field properties to base a fields choices on values from another field. Since that is being set on the field by an Admin it isn't applying the usual view permissions used on records and instead simply pulls over the list of options available and inputs it into the field. This means that your users would see all choices instead of just choices that they have permissions to since all those choices just get loaded into the field.
Typically when a builder is looking to maintain that control we recommend using a join table between the two tables to mimic a multi select field with an editable embedded report on the table B where you are making the choices pulled from the join table. This way you can have users select more then one choice and still control what records they are able to see by the permissions you set in Table A. I hope that suggestion is helpful Scott.
------------------------------
Evan Martinez
Community Marketing Manager
Quick Base
------------------------------