Hi all, I am just wondering what would be the best way to design a qu

Moritz, if you are using strings, you can design your query rule to use the "includes" operator. These inputs can then either be used or unused and should still return valid results. Number and date inputs can be designed as ranges (start input and end input) with all encompassing defaults. If modified they will narrow down results, if unused they would not affect the results.

Hope it helps!
Alex

Hi Alex,

thanks for the hint. I build a query rule with four text parameters, which are all using the includes operator in the query. If I pass in no values at all I am getting back an empty result set. I would have benn expecting the list of all entries or am I misunderstanding how this should be used?

Thanks, Moritz

Never mind. Seems to be working now. I changed some values in my CDT and updated the data store, so I guess there were some inconsistencies for a while.

There seems to be one issue with this approach though. If there is a row that has a null value in one of the queried columns its not being returned.

Yes Moritzw...thats how the includes operator works. It ignores all the null value. Best way of doing it would be writing a stored procedure in DB and calling it in Appian.