Possible to create a task level calculated field to pull in the text from another task custom field? | Community
Skip to main content
M
MariaCr2
Level 3
March 17, 2025
Solved

Possible to create a task level calculated field to pull in the text from another task custom field?

  • March 17, 2025
  • 3 replies
  • 835 views

We have a task custom field that is open text where our team provides updates on the task/ project. I want to know if I can create a calculated field that pulls in what has been entered into that open text custom field?

 

Thanks!

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 Doug_Den_Hoed_AtAppStore

Potentially. I'd have to see it in practice, but it could possibly work for our needs. Would you be able to give me an idea of how to do that? 


 

Hi @mariacr2,

 

I invite you consider this new How to "Echo" post I just created and comment further there.

 

Regards,

Doug

 

 

3 replies

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe Champion
March 17, 2025

if the two objects are separated and not connected in any [downstream] way, no. You wouldn't be able to pull in information from Task 1 into Task 2, for example -- and you wouldn't be able to pull in information from Task 1 into the project it sits in. However, if Task 1 is a parent of Task 2, you might be able to. Or if you place an issue into Task 1, you'd be able to see the information. Or, if you convert Task 1 to Project 3.

Sven-iX
Community Advisor
Sven-iXCommunity Advisor
Community Advisor
March 17, 2025

Yes. You simply reference that field. 

If the custom text field is myTaskField, then your calculated field is 

{DE:myTaskField}

 

Doug_Den_Hoed_AtAppStore
Community Advisor
Doug_Den_Hoed_AtAppStoreCommunity Advisor
Community Advisor
March 17, 2025

 

Hi @mariacr2,

 

Combining the suggestions from @skyehansen and @sven-ix, I'd suggest you move the editable custom form "up" to the Project level so you can then easily reference it in a Task view (read only, mind you) using its DE: syntax.

 

If you instead decide to keep that custom parameter at the Task level (e.g. so it IS editable on a Task view), and also have anything entered then visible on other Tasks within the same Project (read only, mind you; and multiple, if more than one such Task has data entered in that custom parameter), I believe there is a way to then display that information in a Task view or report...but would not recommend it, so will withhold that part unless you need it.

 

Regards,

Doug

M
MariaCr2Author
Level 3
March 17, 2025

Hi Doug - yes, that is what I need. We are putting some parameters in place we wouldn't run into the issues you highlighted, but what we need it to be able to enter info on a task custom form under one task, Tactic Delivery Date (MSD Next Steps task custom form field) and then have what is entered on the custom for, for the Tactic Delivery Date task show in on a calculated field on a separate task within the same project. 

Doug_Den_Hoed_AtAppStore
Community Advisor
Doug_Den_Hoed_AtAppStoreCommunity Advisor
Community Advisor
March 17, 2025

 

Thanks for confirming your requirements @mariacr2, 

 

Although a calculated custom field with that information is not possible (without Fusion / API / etc...and noting that even then it might get "stale"), would showing the Tactic Delivery Date as a column on a Task view or report (as I'd mentioned, noting it would also always be "fresh" data) be of use?

 

Regards,

Doug

Terms & ConditionsAccessibility statement

Loading footer...