You’re offline. This is a read only version of the page.
Mods, please move to the appropriate category as necessary, and/or if this has already been answered please close and point me to the right place.
I am attempting to set table permissions for record at the Account level allowing multiple possible external users to make updates to their records while restricting them to others. The catch is that I do not want to associate the Account table directly to this table to avoid potential variances/mismatches in relationship data. These table records are being grouped by records in a secondary table, and it's that table that's associated to the Accounts table.
The grouping table is needed and used within a separate model-driven app for operational/internal user purposes. And, I cannot just add columns used in the "Grouped By" table and add them to the "Accounts" table because those groupings represent separate interactions that can be had with the same account but at different times, statuses, open and closures, etc.
Share
Report
All responses (
Answers (
50
