Expand my Community achievements bar.

The next phase for Workfront Community ideas is coming soon. Learn all about it in our blog!
SOLVED

Task Report for projects by converted issue originator's home team

Avatar

Level 3

Not sure if this is bad syntax or not a possible filter?  All I know is this throws an error.  Expert advice needed!

 

I'm obviously not an API explorer expert but it looks like I should be able to access the field. 

 

project:status=CUR
project:status_Mod=in
DE:Key Date=Yes
DE:Key Date_Mod=in
project:convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID
project:convertedOpTaskOriginator:homeTeamID_Mod=in

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

great job! It's good syntax (which means you're now officially an API explorer expert), but not a possible filter. 

 

Troubleshooting tips: you can tell it's a good filter, because a similar filter would work in a project report. i.e. the following syntax works in a PROJECT report:

 

convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID
convertedOpTaskOriginator:homeTeamID_Mod=in

 

 

Moving it into your TASK report, now! This won't work, (probably) because it's too many levels? Read this section "Overview of object relationships in Workfront" and tell me what you think. https://experienceleague.adobe.com/docs/workfront/using/reporting/reports/text-mode/create-complex-t... 

 

[Further troubleshooting for masochists: if your code works in a VIEW but not a FILTER then it's too many levels.]

 

Obviously this makes the solution quite clear -- you need to back out your last two lines, and replace it with an exists filter. So take a look at this sample code:

 

EXISTS:a:$$OBJCODE=PROJ
EXISTS:a:ID=FIELD:projectID
EXISTS:a:convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID

 

 

line 1: there exists a project...

line 2: where the project's ID is the same as your task's projectID field...

line 3: and in this project, the original requester's home team is the same as your user's home team.

 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

great job! It's good syntax (which means you're now officially an API explorer expert), but not a possible filter. 

 

Troubleshooting tips: you can tell it's a good filter, because a similar filter would work in a project report. i.e. the following syntax works in a PROJECT report:

 

convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID
convertedOpTaskOriginator:homeTeamID_Mod=in

 

 

Moving it into your TASK report, now! This won't work, (probably) because it's too many levels? Read this section "Overview of object relationships in Workfront" and tell me what you think. https://experienceleague.adobe.com/docs/workfront/using/reporting/reports/text-mode/create-complex-t... 

 

[Further troubleshooting for masochists: if your code works in a VIEW but not a FILTER then it's too many levels.]

 

Obviously this makes the solution quite clear -- you need to back out your last two lines, and replace it with an exists filter. So take a look at this sample code:

 

EXISTS:a:$$OBJCODE=PROJ
EXISTS:a:ID=FIELD:projectID
EXISTS:a:convertedOpTaskOriginator:homeTeamID=$$USER.homeTeamID

 

 

line 1: there exists a project...

line 2: where the project's ID is the same as your task's projectID field...

line 3: and in this project, the original requester's home team is the same as your user's home team.