Forum Discussion
MarkShnier__You
Qrew Champion
It 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
------------------------------
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
------------------------------
MichaelKnecht
2 years agoQrew Trainee
Thats just exactly what was needed. It works. Opens up a wide range of options for us.
Thanks
------------------------------
Michael Knecht
------------------------------
Thanks
------------------------------
Michael Knecht
------------------------------