Search Box parameter for Paginated Report

---

sc27 wrote:

Where can I check for the multi-value parameter option? 

---

So that is really only a consideration if you are using the query builder to create your query and it sounds like you are hand editting your query. But it is a button in the query builder ribbon (see below)

---

sc27 wrote:

Where can I check for the multi-value parameter option? 

 

I was only able to get the text box to work by toggling "Allow blank values" to Yes and setting a default value to blank (I need this as an option as there will be instances where the user will not be inputting anything. 

---

So you are not required to set a default value if you don't want to, having a default will control whether your report waits for input and requires the user to click the button to run the report or whether it renders immediately. So if you want the report to show all data by default when the users first opens it, then they have an option to apply a more restrictive filter then setting the default to blank is fine.

---

@sc2 wrote:

Here is how i coded it -  FILTER( VALUES(Fact[Description]), ( PATHCONTAINS(@Description, Fact[Description] ) )),

 

---

That does not look correct, the PATHCONTAINS function searchs pipe delimited path strings. The way you have it your are searching the parameter using the field value which looks backwards to me.

But even then if you had an expression like PATHCONTAINS( "AB|CD|EF", "CD") it would return true because CD is a value between the | delimiters. However PATHCONTAINS( "AB|CD|EF", "C") would return false since C is not an exact match for any of AB or CD or EF

The way you have it coded it looks like you should be using a function like SEARCH or FIND to see if the parameter value exists somewhere in the Description column.

eg

FILTER( VALUES(Fact[Description]), SEARCH(@Description, Fact[Description]  ) >= 1 )