Cascading Permissions - Is it the answer
Setting the scene I have Regions that have Locations that have Machines that have Tickets. I have cascading permissions set up so that depending on the region the user can see only his/her respect...
Forum Discussion
creating relationships between Managers -> Employees and then Employees -> Tickets is definitely what you need to do. Then you can pull in the Manager to the Tickets table from those relationships.
After that, you can set your permission for Managers to only be able to see the tickets where the current user is the manager shown on the ticket.
------------------------------
Katlyn Allen
kallen@eatatjacks.com
------------------------------
After that, you can set your permission for Managers to only be able to see the tickets where the current user is the manager shown on the ticket.
------------------------------
Katlyn Allen
kallen@eatatjacks.com
------------------------------
I havent figured out how to make that work as that I dont relate the ticket to an employee. I assign the ticket using a dropdown and its just a user field. How can I take that dropdown and turn it into a "relation" I need to keep most of the original framework surrounding the user field because many form rules decide what employee to assign. I havent been able to get form rules to change a related record the same way they change the user field.
------------------------------
Michael Knecht
------------------------------
------------------------------
Michael Knecht
------------------------------
- MarkShnier__You
Qrew Legend
Can you tell us what the Key field is of your Employees table? Is it userid or just Record ID#?
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------- Employee Table key field is the Record ID. If there is a reason to switch it, we can. If it will help in this scenario and in the future
------------------------------
Michael Knecht
------------------------------- MarkShnier__YouIt is very useful to have an employees table where the key field is the userid. If you can make that change then it opens up a lot of possibilities towards what you are trying to do, like know if a ticket is related to a Manager or a Team.
You may want to copy your app to test this first, but if you change the Key field of the Employees table to be the Userid, then you can make a relationship to the tickets and use the existing user field as the reference field. That will keep your existing data all intact. Then you can lookup the Manager down to the employees table.
You can also then have at table of Teams and if you assign employees to a team (can an employee be a member of multiple teams??), then the ticket can know the Team(s) that ticket is involved with and we can figure out how to make a report for the manager for Tickets for their Teams.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
