Using operators in search criteria of a Fusion module

Forum|Forum|9 months ago
May 15, 2025
2 replies
1641 views

Hi!

We like to use the operators available under 'general function' when configuring 'Search Criteria' in Fusion. But we cannot seem to get it to work. Can one of you help us with our query?

1. In case we configure the search criteria like in this screenshot directly below, the scenario works.

2. But as this is the same object and just to different values, we would like to combine this using the 'OR-statement' like seen in the screenshot directly below. However, this config in Fusion returns an error.

Can some determine what we are doing wrong?

Best answer by Sven-iX

Hi @robst

use the "IN" operator: you can feed it a comma-separated list or an array

_Manish_Singh

Level 9

Hello @robst, the OR condition will not work because the API call made from the second method would be invalid. Example, the call would be /TTSK/search?DE:Parent - 3rd level=xyz111&templateTaskID=(abc101)or(def201), which is an invalid API call.

You will need to use the first method. Just think in terms of API call and you'll get an idea of what will work.

R

RobStAuthor

Level 2

Really appreciate the swift response. And if this is how Fusion creates to API call, then this makes sense @_manish_singh.

I would expect this configuration would translate to an API call similar to this. But I am not sure of the Workfront API config can handle this:

/TTSK/search?DE:Parent - 3rd level=xyz111&templateTaskID=abc101&templateTaskID=def201, OR
/TTSK/search?DE:Parent - 3rd level=xyz111&templateTaskID=abc101,def201

Especially this last one seems to be working, looking at the Workfront API documentation (resource: https://developer.workfront.com/tasks.html#get-/task/-ID-).

We are not worried about two different values. But imagine we have multiple values. Hence, our query.

Thanks!

_Manish_Singh

Level 9

Sorry, I was wrong. I did a test on project search using program ID as the criteria. This is what I get:

The run was successful without an error:

This is what the input bundle looks like. It always takes the first OR value from the condition, the second OR condition is not taken in the input.