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

To let Report Definition show string length more than 32



Developers are viewing truncated strings while retrieving data through report definitions. Observing a + sign at the end of string which has more than 31 characters.


This issue is resolved through the following local-change: 

The column size in DB is specified as 32 byte. Hence the data itself is truncated in DB and + sign exists at the end.
There is no issue with Report Definition.

Requested to update the column size and also informed that it is better to use datatype as character than byte.

“If you define the field as VARCHAR2(32 BYTE), Oracle can use up to 32 bytes for storage, but you may not actually be able to store 32 characters in the field, because some of them take more than one byte to store, for example non-English characters.
By defining the field as VARCHAR2(32 CHAR) you tell Oracle it can use enough space to store 32 characters, no matter how many bytes it takes to store each one. A single character may require up to 4 bytes.”


Published July 29, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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