We have a new challenging business requirement. There is a column on the Account entity containing sensitive data. This column shouldn’t be available in any off the Account Views. But users should be able to see the column on the Account Form. I appreciate this sounds a bit odd. But having the column exposed on a View would make it too easy for users to export this column using Excel or taking screenshots etc.
So we thought we could use the Searchable flag on the column configuration (i.e. set it to No). This will hide the column in the Advanced Find selection. But you can still use the Edit Columns function to display it in any of the Views. Apparently, that’s expected behavior (raised this with MS support).
Using Column Level security does not work either. Because it will scramble the field everywhere.
- Is there an option to ‘bypass’ Column Level Security on a Form using JavaScript?
- Is there an Option to run JavaScript on a View to dynamically hide/scramble the column
Can you think of anything else?
Thanks