Expand my Community achievements bar.

SOLVED

Filtering Assignment Report

Avatar

Level 4

I would like to filter an assignment report by the Project Owner's Home Team.

 

Something like this:

project:owner:homeTeamID = 5deaa5330076f8ebbf6b32fd0d1b0ba8
project:owner:homeTeamID_Mod = in

 

This filter does not appear to work though. Any ideas?

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Are you getting a red text error? If so, you might want to upvote this idea:

https://experienceleaguecommunities.adobe.com/t5/workfront-ideas/allow-filters-and-groupings-to-call...

 

The best way to get there is through an exists statement, which you can read up on here:

https://experienceleague.adobe.com/en/docs/workfront/using/reporting/reports/text-mode/create-comple...

 

A sample exists statement might look like this (this is just a guess, I didn't test it):

 

EXISTS:a:$$OBJCODE=PROJ
EXISTS:a:ID=FIELD:projectID
EXISTS:a:owner:homeTeamID=5deaa5330076f8ebbf6b32fd0d1b0ba8

 

 

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Are you getting a red text error? If so, you might want to upvote this idea:

https://experienceleaguecommunities.adobe.com/t5/workfront-ideas/allow-filters-and-groupings-to-call...

 

The best way to get there is through an exists statement, which you can read up on here:

https://experienceleague.adobe.com/en/docs/workfront/using/reporting/reports/text-mode/create-comple...

 

A sample exists statement might look like this (this is just a guess, I didn't test it):

 

EXISTS:a:$$OBJCODE=PROJ
EXISTS:a:ID=FIELD:projectID
EXISTS:a:owner:homeTeamID=5deaa5330076f8ebbf6b32fd0d1b0ba8

 

 

Avatar

Level 4

Thanks Skye!

 

I was on this track as well, but couldn't figure out if I needed to connect to the Project Object (my original thought) or the User Object (my second thought).

 

And the ID=FIELD:projectID always trips me up.

And, as usual, your textmode worked perfectly for my use case!

Avatar

Community Advisor

yeah I hear you, and it's not unusual. Those two things always trip people up. I will leave you with this thought:

 

1) Either object (user or project) might work? It would be an interesting exercise to try the user object to see whether it gives you the same result.

 

2) This line

"EXISTS:a:ID=FIELD:ID"

in my brain, it is better off pictured as 

EXISTS:a:"something on the object"=FIELD:"something on this report"

 

Translation: My exists statement says "hey the ID on the project object is the same as the projectID on this assignment report". You might also be able to say (maybe), "hey, the ID on the user object is the same as the project:ownerID on this assignment report" -- then you would be able to use the user object.