What am I missing? Pulling parent project form info as a calculated task field? | Community
Skip to main content
Christina_Jarosz
Christina_Jarosz
Level 9
January 22, 2023
Solved

What am I missing? Pulling parent project form info as a calculated task field?

  • January 22, 2023
  • 3 replies
  • 1701 views

I'm not sure where I'm going wrong here - I've searched a few posts but no such luck.

 

I'm trying to pull in the field A_B_C from the project, as a calculated field on a task form.

 

I've tried what it seems to be them both the PERIOD and the COLON between the project and field name. 

{Project.A_B_C}

Project.A_B_C

{DE: Project.A_B_C}

 

From a task report, I pulled the text mode of

valuefield=project:A_B_C

but this didnt work either.

 

I'm 99% sure it's something minor but argh!

 

p.s. E-A-G-L-E-S Eagles!

 

Best answer by imgrund

Hi - have you tried {project}.{DE:A_B_C}

 

For calculations and valueexpressions, you separate out the referenced object from the field with the period, but it also needs its own brackets.  (For valuefield, you can just use a colon like you had) 

3 replies

theffernan
theffernan
Level 2
January 22, 2023

It looks like you are using a valuefield, you might try a valueexpression.
https://experienceleague.adobe.com/docs/workfront/using/reporting/reports/text-mode/text-mode-syntax-overview.html?lang=en#valueexpression-syntax-overview-for-views-and-groupings

 

Christina_Jarosz
Christina_JaroszAuthor
Level 9
January 22, 2023

Hmm this seems to reference a view or a grouping. 

 

Is there not a way to capture this in a calcuated field?

Jason_JB
Jason_JB
Level 5
January 23, 2023

I've had to move away from using calculated fields for things like this because they only update when the task is updated - not when the source is updated.  Meaning that the field on the task may show an old version of the project field if:

- project record is updated

- AND task record is not also updated

 

If you're interested, I can share an example of how I'm using Fusion to work around this limitation.

    RandyRoberts
    Community Advisor
    RandyRobertsCommunity Advisor
    Community Advisor
    January 23, 2023

    Yes, please. Thanks Jason!

    Jason_JB
    Jason_JB
    Level 5
    January 24, 2023

    We're making this type of update in the following scenarios:

    • Project to Task (ex: copy related project attribute to task)
    • Task to Project (ex: make the go-live date a project level attribute; sum the value of work delivered based on task attributes)
    • Company to Task (ex: write the Project Company Name to a task field)
    • Company to Project (ex: copy custom data from a company record to the project)
    • Project to Company (ex: sum custom field - value - of projects delivered)
    • Project A to Project B (ex: copy attributes of a related project A to custom data on the project B)
    • Task to Task (ex: maintain what grouping of work child, grandchild, great grand... relate to)

    The purpose for most of these is to support reporting or integration with Salesforce/Jira.

     

    The below example is a combination of project to project and then project to task.

    imgrund
    Adobe Employee
    imgrundAdobe EmployeeAccepted solution
    Adobe Employee
    January 23, 2023

    Hi - have you tried {project}.{DE:A_B_C}

     

    For calculations and valueexpressions, you separate out the referenced object from the field with the period, but it also needs its own brackets.  (For valuefield, you can just use a colon like you had) 

      Terms & ConditionsAccessibility statement

      Loading footer...