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.
Steps to Reproduce
- Create a data table with one property "Multilanguage".
- Expose / optimize the property, and then modify the underlying database column into data type Nvarchar.
- Resave the corresponding Database Table rule.
- 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"
The root cause of this problem is a defect in Pegasystems’ code/rules.
This issue is resolved by HFix-23111.