Roles/Home Pages
Hello everyone! I finished building my first app and I am now starting to build roles/home pages. We have a need for 100 roles and 100 home pages. I'm thinking there must be a simpler way to do t...
Forum Discussion
The right way to do this is to have a table of users and their location. The Key field to that user should be the Userid field.
Then on any table where you need to control access you create a formula user field called [Current User] with a formula of
User()
That function will calculate to the current user. Then lookup the location down to the details table.
Then set up Role Permission with a Custom Rule for these users which are restricted by userid location. Maybe that would be a good name for the Role. "Restricted by userid location"
The Custom Rule would be where [location lookup] = location.
Then you just need 1 Role for those 100 users and 1 Dashboard and one set of those 5 reports.
Then on any table where you need to control access you create a formula user field called [Current User] with a formula of
User()
That function will calculate to the current user. Then lookup the location down to the details table.
Then set up Role Permission with a Custom Rule for these users which are restricted by userid location. Maybe that would be a good name for the Role. "Restricted by userid location"
The Custom Rule would be where [location lookup] = location.
Then you just need 1 Role for those 100 users and 1 Dashboard and one set of those 5 reports.
- Thank you very much! I created the formula user field and it's pulling the user's name. Can you clarify one thing for me please?
"That function will calculate to the current user. Then lookup the location down to the details table."
How do I do this part? My apologies, still kind of new to this. - np, I did leave out a step.
After reconfirming that you haver set the Key field of the Users table to be the userid field, you will make a Relationship between the the Users table and the details table. Do not let the system make the field called [Related User] when you are building that relationship, but instead select the field you created called [Current user].
Feel free to post back if you have any problems. - I don't see the userid field in the Users Table. I currently have Employee Number as the Key Field
- You will need to create a new field called Userid of type User and manually populate it.
Did you already have that table setup and is it already being used in any relationships? - Yes, I already had it set up and I am using it in another relationship to the same table where i created the Current User formula field.
- To make this technique work, you will need to have the Key field be the userid. Can you tell me if for that existing relationship, is the data entry manual? ie are you manually assigning each of your detail records to a user?
- The relationship is a lookup field Where the user technically selects themselves as the person creating the record. I am thinking that can automatically be done to capture the person creating the record too instead of the user selecting themselves from a drop down list of 20k+ people. Currently, they can search for their employee number.
- I suppose that if this is a required field and you are happy with that data entry method of the user selecting themself, then the location lookup can come from that existing relationship.
- If I User Employee Number, do I need to change the formula field I created and use something else instead of user()?
- If I User Employee Number, do I need to change the formula field I created and use something else instead of user()?
