Text mode for column in project report to display non-Primary assignment on specific templateTask? | Community
Skip to main content
-JC
-JC
Level 6
June 12, 2023
Solved

Text mode for column in project report to display non-Primary assignment on specific templateTask?

  • June 12, 2023
  • 2 replies
  • 1588 views

Hi all, looking for help writing the text mode for a column on a project report that displays the non-primary assignment on a templateTask within our project templates. If it's not possible to display just the non-primary assignment, I would also be okay with displaying both assignments (but I can only figure out how show the primary right now). I feel like there's something like assignmentUsersMM...but I can't figure out how to use it in this scenario.

 

Previously, on a task report where the report itself was filtered down to the specific templateTask name, here's what I've used:

 

displayname=Non-primary assignments listdelimiter=<p> listmethod=nested(assignments).lists textmode=true type=iterate valueexpression=IF({isPrimary}=false,CONCAT({assignedTo}.{name})) valueformat=HTML

 

 

How can I translate this into a collection/valueexpression column on a project report?

 

Note, I need this to be on a project report specifically so that the viewers can edit project-level custom fields at the same time. Thank you!



This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by NicholeVargas

Thanks @nicholevargas, really appreciate your insight here and for re-surfacing the suggestion. To clarify, are you saying that both the options of a) splitting the primary and non-primary assignments for a specific task into two columns, and b) showing all assignments for a specific task in one column are not possible in a project report? Thank you!


Both are not possible - you can only pull in the primary assignee of a specific template task into a project report using the text mode below. The reason behind this is due to the IF statement in the valueexpression line.

 

displayname=Non-primary assignments
listdelimiter=<p>
listmethod=nested(tasks).lists
textmode=true
type=iterate
valueexpression=IF({templateTaskID}="aecf4d57065fdb8fe0539260720a5552",{assignedTo).{name})
valueformat=HTML

 

I realize that you need these users to edit project specific fields, but maybe you just have 2 reports side-by-side on a dashboard, 1 task report that shows all the details, and a project report to the right/left so they can in-line edit. @-jc just making sure you saw this, since I edited the reply

2 replies

J_Mas
J_Mas
Level 5
June 12, 2023

I'm not sure I understand @-jc , are you trying to get a task's primary assignee but on a project level report? If so, does that mean you're hoping to see 1 single row per project, with a collection field that lists all the primary assignee's of all tasks within that project?

-JC
-JCAuthor
Level 6
June 12, 2023

Hey @j_mas - almost! I'm hoping for a field on a project-level report that lists the non-primary assignee of a specific task within that project.

 

Let's say the specific task's templateTask:name is "Task 1", and there's two assignees on that task in the project. I need either: one column for the primary assignee and one column for the non-primary assignee, OR one column showing both the primary and non-primary assignees.

 

Does that clear things up? I'm really hoping I'm just overthinking this.

NicholeVargas
Adobe Employee
NicholeVargasAdobe EmployeeAccepted solution
Adobe Employee
June 13, 2023

Thanks @nicholevargas, really appreciate your insight here and for re-surfacing the suggestion. To clarify, are you saying that both the options of a) splitting the primary and non-primary assignments for a specific task into two columns, and b) showing all assignments for a specific task in one column are not possible in a project report? Thank you!


Both are not possible - you can only pull in the primary assignee of a specific template task into a project report using the text mode below. The reason behind this is due to the IF statement in the valueexpression line.

 

displayname=Non-primary assignments
listdelimiter=<p>
listmethod=nested(tasks).lists
textmode=true
type=iterate
valueexpression=IF({templateTaskID}="aecf4d57065fdb8fe0539260720a5552",{assignedTo).{name})
valueformat=HTML

 

I realize that you need these users to edit project specific fields, but maybe you just have 2 reports side-by-side on a dashboard, 1 task report that shows all the details, and a project report to the right/left so they can in-line edit. @-jc just making sure you saw this, since I edited the reply

    VicSellers
    Community Advisor
    VicSellersCommunity Advisor
    Community Advisor
    June 12, 2023

    Hi @-jc! Are the tasks you're referring to related to unique job roles? If so, you could pull in a text mode column based on the job role to the project report. The text mode below is pulling from the People section of the project, which picks up the user's assigned job role on a task.

     

    displayname=Manager

    listdelimiter=<br>

    listmethod=nested(projectUsers).lists

    textmode=true

    type=iterate

    valueexpression=IF({user}.{role}='Manager', {user}.{name})

    valueformat=HTML

    -JC
    -JCAuthor
    Level 6
    June 12, 2023

    Hi @vicsellers! Unfortunately we can't make use of projectUsers for a few reasons - we don't actively manage the Project Users tab if somebody gets dropped from the project, and we also may have multiple users with the same job role on one project. Thanks for trying to approach this from a different angle, though! I'm sure there's got to be a way to get this, somehow...

    Terms & ConditionsAccessibility statement

    Loading footer...