Reference a collection in a project on an assignment report

[MuneerAh2]

Hi everyone, I have the following code that I am using in a project report to show the name of the designer assigned to the project: Switch=to Standard Mode displayname=Designer listdelimiter= listmethod=nested(projectUserRoles).lists textmode=true type=iterate valueexpression=IF({roleID}="7b1cc6e2c1810f6de0530a093a0a97c0",{user}.{name},"") valueformat=HTML width=150 Is there any way for me to use this code or some version of it to find a designer on a project when looking at an assignment report? For example, if I have a task assigned to a writer, but want a designer shown on the same row in the report, how would I do that? Muneer Ahmad

[NicholeVargas]

@Muneer Ahmad As you can reference a project from an Assignment report, you can use a similar format of that text mode code to pull in the name of the Designer associated with the project the assignment is tied to. The only difference would be the bolded line below: displayname=Designer listdelimiter= listmethod=nested(project.projectUserRoles).lists textmode=true type=iterate valueexpression=IF({roleID}="7b1cc6e2c1810f6de0530a093a0a97c0",{user}.{name},"") valueformat=HTML width=150 If you run into any issues, let me know! Nichole Vargas Customer Programs Specialist, Workfront

[AnthonyIm]

One thing that I want to point out with reporting like this that wasn't obvious to me so caused some issues... when you do a collection based on Project Users or Project User Roles, it looks at the Staffing tab of the project or the project team. It does NOT look at the assignments of the tasks. So if someone is removed from a task or swapped, their name will still show up in the report until the project owner goes into Staffing and removes the person. This can cause issues if you have project owners who tend to copy projects instead of creating new ones from a template because all the people from the previous project come over. Just something to think about. Anthony Imgrund FCB