Fusion: Delimiter in filters

[_Manish_Singh]

How do I separate/delimit multiple project status within a single line without relying on the use of an OR condition? Currently, I'm using OR condition (1 status in each section), but the ask is to mention them in same line using a delimiter. Is this possible? I have tried comma and pipe. Thanks!

 

[RandyRoberts]

In a report filter, you would use a tab character "CUR" tab "ONH" tab ect.

That may work in Fusion as well. Sometimes it's difficult to insert a tab in a browser based field though as that usually just tabs to the next field.

If tyou test this, please report back so it may help others.

[_Manish_Singh]

After testing I can confirm applying tabs between status doesn't work. Thank you.

[ChrisStephens]

If I recall correctly, you can do it with comma delimiters, and then change Not equal to either "Not In" or "Does not contain", I can't remember which.

[ChrisStephens · Accepted solution]

This works.

[_Manish_Singh]

Amazing.. this works 

[RandyRoberts]

Hi @ChrisStephens, thanks for this. Your example uses a filter. Have you ever tried something like this in a project search? I tried your example and it doesn't work there. The only way I got it to work was to use an or filter and repeat the Company ID filter, any thoughts?

[_Manish_Singh]

Same question 

I was trying project search today morning, the tip says consider using In/Not In operator, but that doesn't seem like working.

[_Manish_Singh]

To test how project search works, I used API call in postman. Below are my findings:

1) When I use status as two separate params, it gives results successfully as shown below

2) But, when I use status separated by comma (,), it returns empty list

It looks like we need to use OR in this case, because In/Not In doesn't work

[RandyRoberts]

I posted the question over on Make's help site. Maybe someone over there knows the answer.

[ChrisStephens]

That's correct, in the API call you have to create the OR filters, as you've described. A while back I thought this was bugged and asked Workfront and they're response was that it's functioning as intended. So now, for me at least, if I only include the unique filters in the GET request and then use a filter immediately after to filter out my optional parameters.

[RandyRoberts]

That seems to be the only way to do it at this point. Unfortunately, this method returns a lot of records that just need to be filtered out later. Not very efficient so hopefully it gets adressed at some point.

Thanks for noodling with it to find a solution though!