Attempts to run a parameterized report results in no data being reported even though there should be some data that matches your input criteria.
You enter valid parameter values that you know should produce results, yet you still have nothing appearing on the report.
This can be caused by misunderstanding the use of unbound parameters
Diagnosing The Problem
There is a subtle difference in the way bound vs unbound parameters are used in reports. For bound parameters, if you select a value from the lookup you will see that the value will appear with an "=" sign in front of it on the request page. For example a site parameter that is using the site lookup would appear as "=BEDFORD" after you have selected BEDFORD from the list of sites. If you run your report with this, the report will show the results for the selected site.
However, if the site parameter is unbound (and there are some examples of these in our out-of-the-box reports) and you type in "=BEDFORD' as your parameter value, you will see no data on the report.
Resolving The Problem
The reason is that unbound parameters are taken literally as you typed them. Whatever you typed becomes the value. So, in the above example your site is "=BEDFORD' . You obviously don't have a site called =BEDFORD and therefore it fails to pass the sql filter and you get no results.
Use BEDFORD on it's own and your report will execute correctly.
Note that I use a site parameter as an example only. The same would occur for any unbound parameter.-
17 June 2018