Task report, primary assignment status in valueexpression.

hi, this doesn't answer your question entirely, but my guess would be that the "primary assignment" fields you're finding are some sort of short cut on Workfront's side to get at the correct information. I'm basing this guess on looking at the API Explorer task fields and noting that the primary assignment field (in the reference tab) goes to the Assignment section. We know that there can be multiple assignments in one task, so my guess is that the primary assignment is some sort of shortcut where Workfront accessing the collection of assignments and taking the primary details out of it.

As you've noted, you might have slightly less stellar results when you follow this shortcut.

Your pseudo code in your task report should therefore address this by calling on and staying wholly within the collection. It could look something like:

#harrypotterwand: I call on the collection of assignments. (wave your wand after calling it)

While in the collection: if the assignment isPrimary = true, and task status = X and the assignment status = Y, then Z

You would reference this article to call on collections in a View.

https://one.workfront.com/s/document-item?bundleId=the-new-workfront-experience&topicId=Content%2FReports_and_Dashboards%2FReports%2FText_Mode%2Freference-collections-report.html

You would write the valueexpression EXACTLY the way it looks within an assignment report. If it helps you to do so, I often create the assignment report, get the code working, and then copy the valueexpression into the collection of the task report. In other words, in an assignment report the task status is referred to as task:status or {task}.{status} so this is how you would refer to it in your valueexpression. All of the fields I mention above are in the API explorer in the assignment section, so you can reference syntax from there.