BrianRichardso1
6 years agoQrew Trainee
Summarizing users
I'm wrestling with the lack of an option to use a Summary field to pull together a list of Users as defined on a child table. I'm hoping QB adds this type of summary field in the future. In the meantime though...
The Goal: I want to enable the selection of stakeholders for each project, from a table of stakeholders that includes information including a User field matching them to their account.
The Setup: I have a many to many relationship, as follows: Projects < Stakeholder Assignments > Stakeholders
The Ask: I need a summary field at the Projects table that shows all User fields that were assigned to that project in the Assignments table. But there's no Summary field for Users. I know an alternative would be to report directly from the Assignments table on assigned projects, but the Projects table contains reams of data and multiple other relationships that I don't want to replicate as 100 lookups fields on the Assignments table. Plus I'd not have the ability to report on other Project child tables like financials and risks without also setting up a ton of other relationships.
Any tricky ideas? I was playing with the idea of converting user fields to emails and then to text, summarizing that text, then somehow "back converting" those text email addresses to user accounts. But I'm not being successful yet.
------------------------------
Brian Richardson
------------------------------
The Goal: I want to enable the selection of stakeholders for each project, from a table of stakeholders that includes information including a User field matching them to their account.
The Setup: I have a many to many relationship, as follows: Projects < Stakeholder Assignments > Stakeholders
The Ask: I need a summary field at the Projects table that shows all User fields that were assigned to that project in the Assignments table. But there's no Summary field for Users. I know an alternative would be to report directly from the Assignments table on assigned projects, but the Projects table contains reams of data and multiple other relationships that I don't want to replicate as 100 lookups fields on the Assignments table. Plus I'd not have the ability to report on other Project child tables like financials and risks without also setting up a ton of other relationships.
Any tricky ideas? I was playing with the idea of converting user fields to emails and then to text, summarizing that text, then somehow "back converting" those text email addresses to user accounts. But I'm not being successful yet.
------------------------------
Brian Richardson
------------------------------