Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SQL Server Nchar, Nvarchar properties



When using a custom table with exposed Nchar / Nvarchar / Ntext columns, the content appears truncated or corrupted and is retrieved as '?' characters.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create a data table with one property "Multilanguage".
  2. Expose / optimize the property, and then modify the underlying database column into data type Nvarchar.
  3. Resave the corresponding Database Table rule.
  4. Using an activity, set the property value to something containing text that requires Unicode representation (such as "Özhan Arabacıoğlu") the perform an Obj-Save. Observe that data is stored in SQL Server as "Özhan Arabac?o?lu"

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. 


This issue is resolved by HFix-23111.


Suggest Edit

Published August 13, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us