Old case data still showing truncated (32 chars) after optimizing embedded property to 64 chars via Schema Tools

General
, ,
1

I optimized a few embedded properties onto the main work class. By default, the optimized column was created as 32 characters (bytes). I needed 64, so I used Schema Tools to alter the column to 64 characters, then did a Revalidate & Save on the property rule.

After this change:
New cases created after the schema update correctly show the full 64-character value in the optimized column.

Older/existing cases (created before the schema change) still show only 32 characters in that column, the value appears truncated, even though I’d expect the full data to still exist in the BLOB (pzInsKey/storage stream).

Please suggest the solution for inflight scenarios.

2

Hi @SwatiS90 ,

Execute this activity: RecreateIndexesForClass, so that data will get repopulated once again automatically.

I hope this will help you.

Thanks,

Ashok

3

The activity you have mentioned is more about re indexing of the columns in case of page list properties where index table gets created.

In my scenario, the property is single value property inside a page. Please advise.

4

Hi @SwatiS90 ,

Please try to execute Expose API
Syntax
{
“includedClasses”: “LIC-LICAutoI-Work-VehicleInsurance”,
“async”: “false”
}

SystemManagement • v2 • Expose

image
image1351×769 55.8 KB

or

Browse the cases and RecalculateAndSave

Thanks,
Ashok

5

One approach would be to trigger an update/re-save of the affected existing cases so that Pega re-evaluates the optimized property and populates the column with the full value. However, I would recommend confirming the supported Pega approach for bulk backfilling before updating production data directly. @SwatiS90