Want a report that shows all tasks without predecessor relationships | Community
Skip to main content
Level 3
February 9, 2017
Question

Want a report that shows all tasks without predecessor relationships

  • February 9, 2017
  • 17 replies
  • 2556 views
Hello all, I have several projects with tasks that require cross-project predecessors and I want to create visibility on how many tasks are broken per project. I need a report that shows all tasks containing 'Link to' in the name that do not yet have their predecessor. Can anyone help? I'm stuck on the filter to use. Thank you :) -Linden
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

17 replies

Level 2
February 16, 2017
Hi Linden, If I understand you correctly, when you have tasks with "Link To" in the name, they should also have a cross project predecessor? What you're looking for is tasks where "Link To" is in the name, but no predecessor is set? If that's the case, use the following filters: Task > Name >> Contains > Link & Predecessors > ID >> Is Blank Cheers! Heather
Level 10
February 16, 2017
Heather! You’re working the forum? Woooo!
Level 2
February 16, 2017
I just like to jump in and help where I can :)
LindenRhAuthor
Level 3
February 17, 2017
Heather, You understand me perfectly and thank you for the information below. I just tried those filters and my report is still returning no results. I tried just looking for tasks containing ‘link’ and over 1000 tasks appear (which is good) but when I add the ‘Predecessors > ID >> Is Blank’ they all disappear. Not sure what I am doing wrong here? Linden
Level 10
February 17, 2017
Hi: This is a difficult one, in my opinion. You can’t search for something that isn’t there (predecessor ID is blank). The task reference number is the primary key, and acts as a foreign key in the predecessor table. If there are no predecessors for a particular task, then there will be no entries in the predecessor table - in other words, the task reference number would not be found in the predecessor table. You would have to search the Predecessor table for all records where the specific task reference number is not found. I know how to do that through SQL, but not using WorkFront’s reporting engine. WorkFront hides the join behind the scenes in the reporting tool, which is a terribly convenient thing most times. I looked through the Task table and don’t see any attribute that I think tells me there are predecessors. I can’t tell from the task table/object whether it has predecessors or not. The solution might take some text mode work. The obvious answer, to me, is get a snapshot of your database from the AtAppStore.com, drop it into MS Access, and then you can look for the absence of a particular task reference number in the Predecessor table. You can do a lot of other nifty things with that snapshot, too. Sorry, I can’t figure this one out either. Thanks, Eric
Level 2
February 17, 2017
Edited: Apologies, I had forgotten that we were looking for tasks that did not yet have their predecessor filled out. I'm going to keep looking at this to see if we can make it work. Try this text in your filter for the task report: name=Link name_Mod=cicontains predecessors:isCP=true predecessors:isCP_Mod=eq Cheers!
Level 10
February 17, 2017
Hi: Heather - Can you kindly provide the plain English explanation of what each line in your text mode example does? Thanks, Eric ________________________________
Level 2
February 17, 2017
Okay, I think this should work. EXISTS:b:$$EXISTSMOD=NOTEXISTS EXISTS:b:$$OBJCODE=PRED EXISTS:b:successorID=FIELD:ID name=Link name_Mod=cicontains
Level 2
February 17, 2017
Sure! name=Link name_Mod=cicontains These two lines work together to find any task name that contains Link predecessors:isCP=true predecessors:isCP_Mod=eq This is referencing any task where the predecessor is cross project ( isCP ) For the corrected one: EXISTS:b:$$EXISTSMOD=NOTEXISTS EXISTS:b:$$OBJCODE=PRED EXISTS:b:successorID=FIELD:ID What we're doing here is a bit more complex, and to be honest, I'm not sure I can explain it in plain english but I'll try. Since predecessor cannot be called upon without a predecessor being entered, we cannot use Predecessor >> isBlank as I originally hoped. Instead, we are looking for all tasks that there is not a successor to predecessor connection. To break it down, it's easiest to look at it in reverse: EXISTS:b:successorID=FIELD:ID Compares the field successorID on the task table to the ID field on the predecessor table. EXISTS:b:$$OBJCODE=PRED Specifies that we're looking at the predecessor table EXISTS:b:$$EXISTSMOD=NOTEXISTS This is calling at the task level to specify that the previous lines ( predecessor to successor relationship ) do not exist.
Level 10
February 17, 2017
Heather, nicely done. Gold Star for your refrigerator today! What confused me was looking for tasks where the name has the letters “Link” in it. That is the name that the person typed in. When I create predecessors, I don’t put the word Link in it. Going backwards from the successor is clever. Nice. What am I missing? Thanks, Eric