Support Article
Import of Decision Data modifies the propositions incorrectly
SA-59281
Summary
On updating to Pega 7.3 environment, the Import function in Decision Data modifies the propositions in the below two scenarios:
Scenario 1: On exporting and importing the Decision Data without any modifications. This changes the updated column.
Scenario 2: On exporting and importing the Decision Data after modifying a single record in the file. This updates the 'updated by column for all propositions' instead of 'updated by column for a particular row'.
Error Messages
Not Applicable.
Steps to Reproduce
- Update form Pega 7.1.9 to Pega 7.3
- Export the Decision Data
- Check out and import the Decision Data without modifying it. The 'Updated by' column is changed without a change in Data
Root Cause
A defect in Pegasystems’ code or rules. The issue is related to any proposition which has a Date or DateTime property that was created in Pega 7.1.9 version. While exporting the Decision Data in Pega 7.1.9, the Date property is exported to a comma-separated values (CSV) in the 'YYYYMMDD' format.
However, while exporting the same decision data in Pega 7.3, the date property is exported in the 'M/D/YYYY' format. As a result of this, in an upgraded system even if the proposition is not updated, by just an export and import of the Decision Data, the system updates all records due to difference in the format in which the Date property was exported to a CSV file.
Resolution
Apply HFix-42132.Published July 27, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.