Hi WF Community,
I'd like to do the following, when creating a new calculated field on a project form, and wondering how to go about it:
I'm uncertain how to reference fields from a child object.
Short answer is, you can't. Collections aren't accessible in a calculated field's expression.
A calculated field can only reference objects found in the "references" tab of the object in the API Explorer. So a task can reference its project, but a project can't reference its tasks.
If you have Fusion, a scenario can be designed to aggregate your task or issue data within Fusion and then write that to a calculated field on a project form. The expression of that calculated field only references itself so the value can only be overwritten by Fusion.
Thanks, WE. I now recall that information, after you explained it.
We do have Fusion, and that was my backup plan, so thanks for detailing a solution.
Hi @NickVa1 We are running into something similar.
Until the campaign object is released, we are using a workaround for campaign relationships. In other words, we want to tie projects to campaigns in a one to many ability.
In an ideal world, after 1.b above, Workfront would automate and add the newly generated value to a running list that makes up the "Campaign Related" field and which could be used for reporting. Going to post this in the ideas section because it feels like a good workaround if they don't release campaigns.