Question
ING Nederland N.V.
NL
Last activity: 6 Sep 2018 6:19 EDT
Interaction History Record Migration From 7.2.2 to & 7.3.1 Environment
We are working on migrating our Marketing and NBA application’s from 7.2.2 to 7.3.1 environment in 2 phases.
The plan is to migrate Marketing application in first phase and NBA application in second phase
For first phase, we are planning to copy the interaction history as it is to 7.3.1 environment and populate the new columns by using Column populator Utility provided by Pega.
After first phase, Interaction history with same pxFactID value might get created by NBA application (7.2.2) and Marketing application (7.3.1) at same time. What is the best approach to migrate interaction history record generated by NBA application in second phase without any conflicts?
We have around 40 million records now. We expect 2-3 million records to get created in 7.2.2 environment during this period. I couldn't figure out pxFactID generation logic to update the pxFactID (values ranging from -9175856912650182701 to 9175535499679907826) before migrating this delta NBA 7.2.2 interaction history data to 7.3.1 environment during phase 2.
***Edited by Moderator Marissa to update categories***
Accepted Solution
Pegasystems Inc.
IN
Had a discussion internally and closing the loop by responding here as well.
IH data can’t be copied from one instance to another instance since the IH Fact ID’s collision might happen. You can read IH (using pxInteractionHistory DS) data records and write to a flatten table mapped sub class of Data-pxStrategResults (excluding the pxFactID property) using data flow infrastructure.
Copy the flatten table data records from one instance to another instance. And write result to IH from flatten table source using data flow. This way IH Fact ID’s collision can be avoided
Updated: 23 May 2018 11:59 EDT
Pegasystems Inc.
IN
Hi Prakash,
Kindly follow the setps mentioned in the below URL:
https://docs-previous.pega.com/pega-marketing-731-upgrade-guide
Regards,
Rahul
ING Nederland N.V.
NL
Hi Rahul,
Thanks for your response. My requirement about migrating interaction history records in 2 phases is not covered in this upgrade guide.
Regards,
Prakash
Accepted Solution
Pegasystems Inc.
IN
Had a discussion internally and closing the loop by responding here as well.
IH data can’t be copied from one instance to another instance since the IH Fact ID’s collision might happen. You can read IH (using pxInteractionHistory DS) data records and write to a flatten table mapped sub class of Data-pxStrategResults (excluding the pxFactID property) using data flow infrastructure.
Copy the flatten table data records from one instance to another instance. And write result to IH from flatten table source using data flow. This way IH Fact ID’s collision can be avoided