Column generated through optimization wizard not having a value after commit
The optimization wizard was executed on a property called
InventoryItem.ReleaseDate( pyWorkPage belongs to classgroup called CAG-FW-ICFW-Work). This created a new column called releasedate_1 in the database table(work table) and also added the external mapping in the class rule(CAG-FW-ICFW-Work) with the column name mapped to this property.
However, when work items are commited into the work table, some of these records aren’t populating this new column releasedate_1 with the value from the property. The expectation is that Pega should populate this new column with the value from the above property always.. However some records in the table doesn’t have a value for this column eventhough the property in the clipboard has the value.
Interestingly, this never happens in our dev environment and in QA some records have a value in the column and some doesn’t have a value(inconsistent) eventhough the property in the clipboard has this value.
pyWorkPage.InventoryItem.ReleaseDate ( InventoryItem page property is in the work class cag-fw-icfw-work and this inventoryitem page property has a property called ReleaseDate.. This property was optimized using the optimization wizard in pega)
There is another property called ReleaseDate with the same case and type, however this is directly under the work class(CAG-FW-ICFW-Work). This is however not used for optimization.
These 2 properties exists in both the environments(Cox5 and Cox6) and the optimization wizard was run against InventoryItem.ReleaseDate in both the enviroinments. This created a new column called ReleaseDate_1 in the work table and the wizard also added an external mapping for releasedate_1 to inventoryitem.ReleaseDate in the cag-fw-icfw-work class in both the environments.
The column releasedate_1 is consistently getting populated in dev, however in QA some records have a value for this column and some doesn't have a value for this column(inconsistent).
I believe this is a known problem. Suggest you to enter an SR and someone in GCS can help validate if this is working as designed.
At the very least we need to inform the user about the duplicate properties rather than having this inconsistent issue. You may also try removing the property that is not desired and try running the optimization tool.