Question
Coforge DPA UK Ltd.
IN
Last activity: 11 Jul 2023 11:25 EDT
Pega Interaction History not working after dropping the extended column from Channel Dimension table
I have a requirement where I extended Interaction History's channel dimension table by adding new column.
Updated the OOTB data transform pyInteractionHistoryConfiguration to include the new added column. Everything has worked as expected i.e., The new column is being populated with the values without any issues.
Now as part of our organisation process, we dropped the column to test backout scipt & created it again. Now the issue is it is not working at all i.e., even though I'm passing value to the newly added column, it is empty in the channel dimension table.
I tried to clear the cache, restart application server, saved the database table instance etc. but nothing is helping us. I don't understand how the Dimension tables are working. I cleared all the data from channel table and tried, in Fact table the row is having the pzchannelID with old value but the same reference is missing in Channel dimension table.
Any suggestion or help would be appreciated please.
***Edited by Moderator Marije to change type from Pega Academy to Product, added Product details and Capability tags****
Pegasystems Inc.
GB
@DurgaraoJeeri The issue could be due to an incomplete or incorrect configuration process.
To properly extend the Interaction History table, you should follow these steps:
- Create the properties you want to add in the appropriate interaction history class (Fact or Dimension).
- Create matching columns in the appropriate interaction table (Fact or Dimension).
- Update the Data-Decision-IH-Configuration.pyInteractionHistoryConfiguration data transform in your Artifacts ruleset to add the new properties created in step 1.
- Create the matching properties in the Proposition Management Hierarchy.
- Update the Data-Decision-IH-Configuration.MKTInteractionHistoryExtension data transform in your Artifacts ruleset to add the new properties created in step 1.
- Re-save the corresponding Database Table rule for the interaction class where you added the properties.
If you have missed any of these steps or made an error during the process, it could cause the issue you are experiencing.
Check out
Extending the Interaction History table for the CaptureResponse service
Pegasystems Inc.
GB
@DurgaraoJeeri please can you mark reply as 'Accept Solution' if your issue is resolved?