https://community.appian.com/discussions/f/rules/814/hi-all-i-am-just-wondering-what-would-be-the-best-way-to-design-a-quHi all, I am just wondering what would be the best way to design a query of a datastore with dynamic search parameters? If I use query rules I have to create X! query rules for X possible search parameters. Is there a way to inject dynamic sql into aen-USTelligent Community 12https://community.appian.com/thread/2761?ContentTypeID=1Fri, 07 Jun 2013 12:07:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:e137c0c8-3989-49f3-8c8e-8fb2af41d504subhankarbYes 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.<div style="clear:both;"></div>https://community.appian.com/thread/2726?ContentTypeID=1Wed, 05 Jun 2013 13:49:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:beeb08b3-16e5-4f23-81d6-ab297d77005emoritzwThere 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.<div style="clear:both;"></div>https://community.appian.com/thread/2725?ContentTypeID=1Wed, 05 Jun 2013 12:32:32 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:ecd50c86-2aca-43e8-b0b7-640bb487685amoritzwNever 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.<div style="clear:both;"></div>https://community.appian.com/thread/2724?ContentTypeID=1Wed, 05 Jun 2013 12:26:42 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:15741662-2bdb-4d5d-92bc-61f5be7597f0moritzwHi Alex,<br /><br />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?<br /><br />Thanks, Moritz<div style="clear:both;"></div>https://community.appian.com/thread/2718?ContentTypeID=1Tue, 04 Jun 2013 19:46:39 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:9e2afec7-a0a4-468d-bdc0-3a3a44e8b6a6Alex WellerMoritz, if you are using strings, you can design your query rule to use the &quot;includes&quot; 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.<br /><br />Hope it helps!<br />Alex<div style="clear:both;"></div>