We have a report definition that uses a parameter in its only filter. We have checked the box " use null if empty".
When we run the report without providing a parameter, it returns zero results. Which is expected, the filter blocks all records as the parameter is not filled in.
Now we have a datapage with the same (not mandatory) parameter, which is loaded by the report given above. We use "pass current parameter page". If we run the datapage without providing a parameter, the datapage is loaded with all records in the table. In other words: the filter is not working. This is an unexpected result.
We can think of a workaround, but we were wondering if somebody has experienced this before, and if this is a bug in Pega?
(Changing the "pass current parameter page" to passing the actual parameter does not change the situation sketched above)
***Edited by Moderator Marissa to update Capability tags****
@RobertJanStreng By any chance , have you looked at the count of records retrieved by the data page, Robert. There is a possibility that the report would be retrieving the records with column value as null, as we are enabling "Use null if empty" checkbox.
We can confirm this by comparing the count of total records in table with the count of records fetched by datapage( using pxResultscount value).