Support Article

Filter Condition on Report Definition Rule Does Match Unicode



A query is generated by PRPC report definition rule with parameters passed for FirstName and LastName. Even though records exist in database, they do not match.

Error Messages

Not Applicable

Steps to Reproduce
  1. Create database table with two columns, first name and last name, in MS-SQL Server Database with column type nvarchar.
  2. Create a record in this table with first name and last name in unicode Char.
  3. Create a data class instance, Data Admin database Table Instance and map the table to class.
  4. Create a report definition rule on that class with two filter conditions for first name, last name and matching names in unicode Char.
  5. Observe that the records do not match.

Root Cause

A defect in Pegasystems' code or rules:
Nvarchar column type is not set correctly in the column. Thus, N is not prefixed to the prepared value for NVarchar column in SQL Server database.


Apply HFix-31396.

Published January 9, 2017 - Updated January 30, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.