If you’ve ever filtered<\/SPAN><\/B> the data within the report using reporting services GUI, you may have realized that \u201c%\u201d as an escape character (wildcard) won\u2019t work and <\/SPAN>you need to replace it with asterisk(\u201c*\u201d) instead.Let\u2019s say you want to filter a field of the dataset called \u201cFields!Employees_Name.Value\u201d to only contain employees whose first names start with \u201cJo\u201d. Obviously there are two ways to do so:<\/P> Well, I usually go for the first option, but there are some cases that your data source is shared between couple of containers in your report and you cannot filter it from the scratch. In these circumstances you got to define custom filters on container you wish to show data in it.If you right click on the table object in the report designer, select properties and choose the \u201cFilter Tab\u201d ,you can define the filters there using different operators ( = ,<>,Like and etc) . In our example we expect something like <\/P> <\/SPAN>Expression <\/SPAN>Operator <\/SPAN> <\/SPAN>Value <\/SPAN>Fields!Employees_Name.Value <\/SPAN> <\/SPAN> <\/SPAN>Like <\/SPAN> <\/SPAN>Jo% <\/SPAN>(WRONG)<\/P> Amazingly this doesn\u2019t work.I don\u2019t understand why the standard T-SQL escape characters are changed in reporting services for Like operator!? , but the right way of doing that is as follow:<\/P> <\/SPAN>Expression <\/SPAN>Operator <\/SPAN> <\/SPAN>Value Fields!Employees_Name.Value <\/SPAN> <\/SPAN> <\/SPAN>Like <\/SPAN> <\/SPAN>\u201cJo*\u201d <\/SPAN>(RIGHT)<\/P> Now the question is what if I want to filter all the names starting with \u201cJo\u201d OR \u201c<\/B>Te\u201d?.First thing you may do is to add another line, and then you are tapped because GUI by default \u201cAND\u201d the conditions instead of \u201cOR\u201d and the GUI doesn\u2019t let you change \u201cAND\u201d to \u201cOR\u201d, because the operator \u201cLIKE\u201d requires exactly 1 and only 1 filter value.If you still want to have a wildcard in both statements, then I guess you cannot do it in that way (you\u2019d better change your data source to return the filtered data), but if you know exactly what you are looking for then there is a workaround which is directly changing the RDL (XML \u2013Formatted) code. You need to use operator \u201cIN\u201d instead of \u201cLike\u201d as follows:<\/P> If you’ve ever filtered the data within the report using reporting services GUI, you may have realized that \u201c%\u201d as an escape character (wildcard) won\u2019t work and you need to replace it with asterisk(\u201c*\u201d) instead.Let\u2019s say you want to filter a field of the dataset called \u201cFields!Employees_Name.Value\u201d to only contain employees whose first names start with […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-1107","post","type-post","status-publish","format-standard","hentry"],"yoast_head":"\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
<Filter>
<FilterExpression>=Fields!Employees_Name.Value<\/FilterExpression>
<Operator>In<\/Operator>
<FilterValues>
<FilterValue>John<\/FilterValue>
<FilterValue>Johan<\/FilterValue>
<FilterValue>Johnoton<\/FilterValue>
<\/FilterValues>
<\/Filter>
<\/Filters><\/o:p><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"