Hi John, I'd suggest you read up on Referencing "https://support.workfront.com/hc/en-us/articles/115000586214-Referencing-Collections-in-a-Report">Collections in a Report , and with those concepts in hand, for each of the special column's you seek (e.g. Content Due from Client ) iterate through the Task Names in the Project, ignoring (e.g. by displaying nothing ) all but the one pertaining to the particular special column (e.g. Provide editorial assets ), and showing whichever date matters for that Task in the particular special column (e.g. Planned Start Date ), which would look something like this, noting that there are a variety of "https://community.workfront.com/discussions/community-home/digestviewer/viewthread?MessageKey=60cc6386-d10c-4043-b37f-95f37a48224a&CommunityKey=ccf3381b-a473-4ef2-9f81-4dd3244cf522&tab=digestviewer#bm60cc6386-d10c-4043-b37f-95f37a48224a">listdelimiter options :
displayname= Content Due from Client
listdelimiter=
listmethod=nested(tasks).lists
textmode=true
type=iterate
valueexpression=IF( {name} =" Provide editorial assets ",{ plannedStartDate }, "" )
valueformat=HTML
Provided there's only one Task Name that matches within the Workplan, the result should be the appropriate single date in each special column . BONUS TIP: if it is common for Project Managers to edit these special Task Names (e.g. by adding a suffix with more details; handy, but totally breaks this concept), assuming this is a standardized workflow that you govern using Templates, instead of checking the {name} of the Task (which might have been edited), it's more trustworthy to check the {templateTask}.{name} for the same special Task Name since the Template Task Name is more stable. Regards, Doug Doug Den Hoed - AtAppStore Got Skills? Lend a hand!
https://community.workfront.com/participate/unanswered-threads