Task Report - Only Display Cross Project Predecessor Tasks | Community
Skip to main content
N
NRYNR
Level 10
March 16, 2018
Question

Task Report - Only Display Cross Project Predecessor Tasks

  • March 16, 2018
  • 5 replies
  • 991 views

Hi all,

Let's say I have: "Master Project" with "Task B" and "Task B" has a cross-project predecessor defined as "Sub Project","Sub Project Task 3". My task report on the master project works great. That code is outline below. What I need is the reverse, which is a task report on "Sub Project" showing me all tasks that are predecessors to other projects. And, show those other projects in the view.

Any thoughts?

-------------------------------------------------------------------

Master Project

  • Task A
  • Task B
  • Task C - Sub-Project Predecessor = "Sub Project - Task 3"

Sub Project

  • Task 1
  • Task 2
  • Task 3 - Predecessor to "Task C"

Task Report on Master Project

  • Filter
    • Tasks in master project "Master Project"
    • Cross-project predecessors is true
  • View
    • Task Name "Task C"
    • Cross-Project Predecessor - Project Name "Sub Project"
    • Cross-Project Predecessor - Task Name "Task 3"

Successful Result

  • Filters
    • projectID=aasdf087asdf0987asdf

projectID_Mod=in

  • View
    • Task > Name
    • displayname=Predecessor Project Name

listdelimiter=

listmethod=nested(predecessors).lists

textmode=true

type=iterate

valueexpression=IF({isCP}="true",{predecessor}.{project}.{name})

valueformat=HTML

  • displayname=Predecessor Task Name

listdelimiter=

listmethod=nested(predecessors).lists

textmode=true

type=iterate

valueexpression=IF({isCP}="true",{predecessor}.{project}.{name})

valueformat=HTML

  • displayname=Predecessor Task Name

listdelimiter=

listmethod=nested(predecessors).lists

textmode=true

type=iterate

valueexpression=IF({isCP}="true",{predecessor}.{name})

valueformat=HTML

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

Doug_Den_Hoed__AtAppStore
Community Advisor
Doug_Den_Hoed__AtAppStoreCommunity Advisor
Community Advisor
March 17, 2018

Hi Narayan,

I'm tempted to ask for a mock up of what you'd want the Sub Project report to look like, but instead, will first suggest that you check out this related thread from a couple of weeks ago. It dealt with Successors, and -- in case it solves your problem -- might make that screenshot less of a set up and more of a punchline.

Regards,

Doug

N
NRYNRAuthor
Level 10
March 24, 2018
Thank you Doug. This helped me understand that we can pull in successor information. However, I don't think there's a way to distinguish tasks (filter) where the successor task is in a different project due to the inability to filter on collections that I'm aware of. I was hoping for a task report only showing tasks that were the "resolving tasks" of tasks of other projects.
M
melindal3825541
Level 5
April 10, 2018

OK, crazy exists mode syntax (because I had this same problem today)

Task Report for Tasks with Cross Project Successors

Filter:

EXISTS:a:$$EXISTSMOD=EXISTS

EXISTS:a:$$OBJCODE=PRED

EXISTS:a:isCP=true

EXISTS:a:predecessorID=FIELD:ID

Successor Project: Task Column:

(remove spaces from the < p > )

displayname=Successor Project: Task

listdelimiter=< p >

listmethod=nested(successors).lists

textmode=true

type=iterate

valueexpression=CONCAT({successor}.{project}.{name},": ",{successor}.{name})

valueformat=HTML

And the Opposite

Task Report for Tasks with Cross Project Predecessors

Filter:

EXISTS:a:$$EXISTSMOD=EXISTS

EXISTS:a:$$OBJCODE=PRED

EXISTS:a:isCP=true

EXISTS:a:successorID=FIELD:ID

And Column:

displayname=Predecessor Project: Task

listdelimiter=< p >

listmethod=nested(predecessors).lists

textmode=true

type=iterate

valueexpression=CONCAT({predecessor}.{project}.{name},": ",{predecessor}.{name})

valueformat=HTML

N
NRYNRAuthor
Level 10
April 12, 2018
Excellent! Thank you.
N
NickVi2
Level 2
May 9, 2018
Thank you! This was exactly what I was looking for. Nick Vivanco
Terms & ConditionsAccessibility statement

Loading footer...