How to "Echo" Custom Data between Object Peers (e.g. Tasks within a Project) | Community
Skip to main content
Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity Advisor
Community Advisor
March 18, 2025

How to "Echo" Custom Data between Object Peers (e.g. Tasks within a Project)

  • March 18, 2025
  • 5 replies
  • 1303 views

 

Hi Folks,

 

Based on this interesting challenge from @mariacr2, I'm pleased to share the following technique to easily edit a custom data parameter (e.g. a Tactic Delivery Date on a particular Task) and have it "echo" to its peers (e.g. all other Tasks on the same Project), without Fusion, and always kept "fresh" after each page refresh.

 

Here's the textmode for the final column, noting that the trick is to go "up" (on a Task report or view) to each project.tasks in the nested listmethod:

 

displayname=Other Tactic Delivery Date(s) type=iterate listdelimiter=<p> listmethod=nested(project.tasks).lists valueexpression={DE:Tactic Delivery Date} valueformat=HTML

 

You could make the valueexpression more sophisticated (e.g. IF, CONCAT, etc.), and in a similar fashion, you could echo custom data between Issues on a Task or Project, Projects in a Program or Portfolio...lots of potential.

 

Enjoy, have fun, and if you put it to good use, I'd appreciate hearing about it.

 

Regards,

Doug

 

 

    5 replies

    -JC
    -JC
    Level 6
    March 20, 2025

    Don't have a use case for this right now, but also didn't think this was possible, so wanted to say thanks Doug!

      Doug_Den_Hoed__AtAppStore
      Community Advisor
      Doug_Den_Hoed__AtAppStoreCommunity AdvisorAuthor
      Community Advisor
      March 31, 2025

       

      Hi @brianha3,

       

      I spotted your Report that pulls project - and related projects in same programs post, and wonder if it might be a good use case for my "Echo" technique above.

       

      Imagining a "Parent Project Info" custom data parameter that gets populated only on each "Parent" Project within a Program, as you described, and noting that in this case it is the program. prefix in the listmethod performing the miracle, I'd suggest something like this:

       

      displayname=Parent Project Info type=iterate listdelimiter=<p> listmethod=nested(program.projects).lists valueexpression={DE:Parent Project Info} valueformat=HTML

       

      If you end up trying it, I'd be interested to hear how you make out.

       

      Regards,

      Doug

       

      cc  @scottmo1 -- tagging you for similar proHa consideration...

       

       

      B
      BrianHa3
      Level 2
      March 31, 2025

      Hi Doug. I think I must have missed your more specific instructions above when I replied previously on my post. Let me give this a try! Thanks so much!

      B
      BrianHa3
      Level 2
      March 31, 2025

      Doug...this is awesome! This is SUPER helpful. I can't exactly "filter" with this from within Workfront (that I can figure out yet). But having the ability to tie data from the "parent" project to the others within the Program give me a lot of options on things we can do. Greatly appreciate your assistance!

      Doug_Den_Hoed__AtAppStore
      Community Advisor
      Doug_Den_Hoed__AtAppStoreCommunity AdvisorAuthor
      Community Advisor
      March 31, 2025

       

      Hi folks,

       

      Last week, @mariacr2 and I recorded this short podcast showing how this new "Echo" technique can be applied to the longstanding Project vs Task Level update requirement.

       

      Enjoy, and I look forward to any follow up conversations and ideas you'd like to share on this post.

       

      Regards,

      Doug

       

       

       

      cc @jon_chen, as mentioned...

        Doug_Den_Hoed__AtAppStore
        Community Advisor
        Doug_Den_Hoed__AtAppStoreCommunity AdvisorAuthor
        Community Advisor
        April 6, 2025

         

        Hi @ericsa7 and @kurt_jones,

         

        As I mentioned on Eric's related Default task value based on parent task post, I am pleased to share this non-Fusion alternative that uses my Echo technique to meet the requirements.

         

        Where the original challenge from @mariacr2 needed an Echo to project.tasks, and then the next challenge from @brianha3 needed an Echo to program.projects, this one needed an Echo to parent.children:

         

        displayname=Echo Top Parent Custom Parameter listdelimiter=<p> listmethod=nested(parent.children).lists type=iterate valueexpression=IF(RIGHT({wbs},2)=".1",CONCAT({parent}.{parent}.{DE:Top Parent Custom Parameter},{parent}.{DE:Top Parent Custom Parameter},{DE:Top Parent Custom Parameter})) valueformat=HTML

         

        It took me a couple of extra days (and several failed lightbulb attempts) to invent the IF(RIGHT({wbs},2)=".1" part, which restricts the Echo to only appear ONCE within a certain level by only Echoing for the FIRST (".1") subtask, as defined by the Work Breakdown Structure (WBS), since There Can Only Be One...ehm...one. With that in hand, though, it neatly meets the requirements, in real time, no Fusion required, as shown below.

         

        Keep the cool challenges coming, and if you figure one out yourself, you're welcome to share it here, too!

         

        Regards,

        Doug

         

         

         

          Doug_Den_Hoed__AtAppStore
          Community Advisor
          Doug_Den_Hoed__AtAppStoreCommunity AdvisorAuthor
          Community Advisor
          April 7, 2025

           

          Hi @12409510,

           

          As I mentioned on your Next Subtask Column in Task Report post, I invite you to consider adding the project. prefix to your original attempt, to go "up, then down" in order to Echo all of the Tasks of interest to all other Tasks.

           

          description=Tasks Ready to Start displayname=Next Task(s) listdelimiter=<div> listmethod=nested(project.tasks).lists type=iterate valueexpression=IF({canStart}&&{status}!='CPL'&&{status}!='NOT'&&{numberOfChildren}=0,CONCAT("•",{name})) valueformat=HTML

           

          Regards,

          Doug

          Terms & ConditionsAccessibility statement

          Loading footer...