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
Scott,
100% agree with Evan.
I have a personal vendetta against multi select fields for a variety of reasons. I urge you to always build a new table and relate it as a Parent instead of using a multi select.
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------
100% agree with Evan.
I have a personal vendetta against multi select fields for a variety of reasons. I urge you to always build a new table and relate it as a Parent instead of using a multi select.
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------
- Appreciate the feedback Don and Evan. I guess my focus is more on the use of the 'Shared field' concept and that role-based data rules don't appear to apply to that concept. My assumption is this behavior would be the same if I was using the 'Shared field' concept as part of a multiple choice field...
So good feedback on using relationships for the specific scenario- but still have a concern that the 'shared field' concept appears to be a loophole around Role based data visibility rules- such that I need to go back and and review all uses of Shared fields across my apps...
Seems like since such effort was put into the data visibility rules it should be the 'end-all-be-all' anytime a user is viewing data
------------------------------
Scott Pugh
------------------------------
