Forum Discussion
ShawnRenn2
7 years agoQrew Trainee
The best way to account for this would be a "Many to Many" relationship where what you're reporting on is the unique assignment/types a user may have for any particular "record".
When reporting on a single table, a column can only summarize a single record once, or not at all based on the filters you apply to that report.
Lets assume the table you're assigning these users as either "Assigned to", "Transferred to" and/or "Reassigned to" is called "Tickets". A single ticket record is unique, and having 3 different user fields will only allow you to summarize that ticket based on one of them.
If however you you had a table called assignments where you connected the user, their "Assignment Type" and the Ticket, you could then run a report from the assignments table where that user/assignment is unique, and the # of "Tickets" to which they were assigned is not.
Your reports would look like this....
Hope this helps.
When reporting on a single table, a column can only summarize a single record once, or not at all based on the filters you apply to that report.
Lets assume the table you're assigning these users as either "Assigned to", "Transferred to" and/or "Reassigned to" is called "Tickets". A single ticket record is unique, and having 3 different user fields will only allow you to summarize that ticket based on one of them.
If however you you had a table called assignments where you connected the user, their "Assignment Type" and the Ticket, you could then run a report from the assignments table where that user/assignment is unique, and the # of "Tickets" to which they were assigned is not.
Your reports would look like this....
Hope this helps.