Reports executed using the SDK invert parameters or cause Dynamic Query to throw XQE-PLN-0537

Summary

Reports executed by using the SDK throw exception XQE-PLN-0537.

Example:
XQE-PLN-0537 The inverted parameter 'p1' can only be used in the context of an IN or IN_RANGE operator. Context is 'nullif([tpch].[CUSTOMER].[C_NAME]; 'Customer#000000002') > ?p1?'.

Reports executed using the SDK return incorrect results due to the parameters inverted.

For example:
A filter T.c1 in ('a') is converted to T.c1 not in ('a')

Both issues are due to an SDK defect.
PH30162 REPORTS EXECUTED VIA SDK RESULT IN INVERTED PARAMETERS AND FAIL WITH XQE-PLN-0537.


Reports that are executed from the user interface always set the inclusive property to true, while the SDK was setting the property to false. The SDK fix initializes the property to true so that reports are executed with it set to true.

Report views created and saved with parameter values that use the SDK with the defect, can continue to have the same issues. When report views were created and saved, the parameter values were also saved in the Content Store with the inclusive property serialized incorrectly to false.

After applying solution for APAR PH30162, re-create the report views that use the SDK or apply the following manual steps.

Using the Cognos Analytics portal, reset the parameter values.

1. Edit the Properties of the view.
2. Select the Report tab.
3. Select Set Values
4. Select Set
5. Enter the values when prompted.

This procedure resets the inclusive property to true.