Forum Discussion
This can be done by creating a filter which says Ask the user.
------------------------------
Prashant Maheshwari
------------------------------
- MarkShnier__You3 years ago
Qrew Legend
My solution to this was to have two tables. The main table holds non confidential info. The other table is a Parent to the main table and has confidential information, values from the confidential table are looked up down to the main table.
All employees have access to the main table but the confidential table has restricted access rules..
The effect us that the main table does not reveal the confidential fields to the restricted users.
So no pipelines and no double entry of data.
Just need a button to create the missing Parent or Child depending on how you want to do your workflow for new employees. It's also pretty easy to initial the second table by copying the first table
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------- JenniferMeyer3 years agoQrew MemberMark,
I originally did that and the parameters from the "Employee Table" carried through to the "Employee Database Table".
Are you saying I should switch them around? Make the "Employee Database Table" the main table and the "Employee Table" the confidential table? I could see how that could work.....
------------------------------
Jennifer Meyer
------------------------------- MarkShnier__You3 years ago
Qrew Legend
Well, you want to arrange it so the confidential data is in the parent table so it can be easily looked up down to let's call it the main table. Then people who view the main table will or won't see the confidential data depending on their permissions for the confidential data table.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------