Using operators in search criteria of a Fusion module

[RobSt]

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?

[_Manish_Singh]

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.

[RobSt]

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]

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.

So even if it runs, it won't apply the second OR condition.

[_Manish_Singh]

It is better to use custom API call module in this case rather than using the search module.

Example: PROJ/search?programID=57fe4e10005c08ca1a213f7237904c89&programID=57fe4e58005c10c5742c09aba18334d1

[RobSt]

Thx again, Manish! So, is it safe to conclude adding operators available under 'general function' when configuring 'Search Criteria' in Fusion don't work as expected? If that is the case, I do agree. Creating a custom API call makes sense.

[_Manish_Singh]

Yes, please proceed with the custom API module. It will be easier to manage in the future if additional criteria are added.

[RobSt]

Thx Manish!

[Jackwi5]

Hi @RobSt,

You're absolutely right — using the OR condition like that breaks the structure of the API call, making it invalid. I faced a similar issue recently while working with nested filters and had to stick with the first method too.

Thinking in terms of how the API parses parameters really helps. Structuring the request properly is key, especially when dealing with multiple conditions.

On a side note, while working on a filter system for a product range like (https://www.eliquidbase.co.uk/collections/disposable-vapes), I had to manage something similar — multiple attribute filters where only one method gave valid results.

[Sven-iX · Accepted solution]

Hi @RobSt 

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

[RobSt]

Thx a lot @Sven-iX , they array worked like a charm using the IN operator. 

Appreciated!