HeatherBryant2
6 years agoQrew Assistant Captain
Using Test as Role versus App-wide Filters
The main table of my app is Clients. Clients is the parent to 10 tables. When a Client account is closed, there is a 'Closed' checkbox. I carry this checkbox to all my other tables and typically would filter in each report to not show records where the Related Client has Closed marked as True, except in one report which would filter to only show those Related Clients' records.
It's not hard for me to implement that filter, but sometimes annoying. And, more so, for my users who create personal reports and don't know or remember to always implement that filter, it can be unfriendly.
I was wondering if I should filter at the Role level, to not show records where the Related Client has Closed as true. And then create a separate role called 'View Closed Clients', where users could switch to that role (all my users that need to see closed records have the ability to Test as a Role).
What do you all think about that?
------------------------------
Heather Bryant
------------------------------
It's not hard for me to implement that filter, but sometimes annoying. And, more so, for my users who create personal reports and don't know or remember to always implement that filter, it can be unfriendly.
I was wondering if I should filter at the Role level, to not show records where the Related Client has Closed as true. And then create a separate role called 'View Closed Clients', where users could switch to that role (all my users that need to see closed records have the ability to Test as a Role).
What do you all think about that?
------------------------------
Heather Bryant
------------------------------