Question

1
Replies
1282
Views
Close popover
Michael Fede (MichaelF4652)
Raytheon Technologies

Raytheon Technologies
US
MichaelF4652 Member since 2016 17 posts
Raytheon Technologies
Posted: August 3, 2018
Last activity: August 3, 2018
Closed

Best Practice for Optimized Properties

We have run into an issue where our customer would like to see property values that are longer than 32 characters in reports.

Found this article that explains why values with more than 32 characters are being truncated and how to update the database columns to solve the problem: https://community.pega.com/support/support-articles/full-description-not-displaying-particular-column

This article is a few years old and tagged with Pega Platform version 6.2. We are in the process of upgrading from version 7.3 to 7.4. Is there a better approach to solve this problem in the newer versions of the platform?

I expect that the columns for optimized properties are set to be VARCHAR(32) for a reason, is it a best practice to increase the size of these columns? Is there anything we should be cautious of when doing this?

Is there any way to specify the size when optimizing the property instead of having to go back and manually updating the database column after the property is optimized?

Pega Platform Low-Code App Development Reporting Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.