Expand my Community achievements bar.

Don’t miss the Workfront AMA: System Smarts & Strategic Starts! Ask your questions about keeping Workfront running smoothly, planning enhancements, reporting, or adoption, and get practical insights from Adobe experts.
SOLVED

Wildcard within IF expression in nested collection

Avatar

Level 3

I'm having trouble getting a user wildcard to work in a valueexpression within a nested list statement. My end goal is to show a column with all those co-assigned to a user's tasks, but not show their own name.  Using the collection of Assignments within a task, I can make this code work and it correctly lists only the other people that are co-assigned with the user with that specific ID:

 

displayname=Co-Assignments
listdelimiter=<p>
listmethod=nested(assignments).lists
type=iterate
valueexpression=IF({assignedTo}.{ID}="5d13826400d6f67f13d0f5847989da56", "", CONCAT({assignedTo}.{name}))
valueformat=HTML

 

But when I switch out the hard coded ID number for the variable $$USER.ID the column is blank.

 

displayname=Co-Assignments
listdelimiter=<p>
listmethod=nested(assignments).lists
type=iterate
valueexpression=IF({assignedTo}.{ID}=$$USER.ID, "", CONCAT({assignedTo}.{name}))
valueformat=HTML

 

I've also tried "$$USER.ID" and {$$USER.ID} to no avail. Does anyone know if the syntax of this wildcard is wrong when used in an IF statement or why the variable wildcard would not work?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 6

I kept testing this and couldnt get the wildcard to work in the calculation. I decided to look at the documentation and found this snippet:  "Wildcard filter variables are not supported when referencing nested collections in a calculated column". Unless Im misinterpreting the verbiage it looks like you cannot use the wildcard in the collection. 

Link:  Wildcard filter variables | Adobe Workfront

View solution in original post

3 Replies

Avatar

Level 6

Looking at the API Explorer I'd try using {assignedToID} not {assignedTo}.{ID}.

Avatar

Correct answer by
Level 6

I kept testing this and couldnt get the wildcard to work in the calculation. I decided to look at the documentation and found this snippet:  "Wildcard filter variables are not supported when referencing nested collections in a calculated column". Unless Im misinterpreting the verbiage it looks like you cannot use the wildcard in the collection. 

Link:  Wildcard filter variables | Adobe Workfront

Avatar

Level 3

Hmmm, well that's certainly disappointing. I appreciate you looking at it and finding this answer. It was driving me crazy.  Thanks.