We are using pega as a decision service to do a web campaigning. We need to store all the interaction id's into IH_Fact table. We don't restrict duplicate entries with the same interaction id into IH_Fact. What happens if I change the primary key of the IH_Fact table (pxFactID to pxInteractionID). I know the reason for having pxFactID as the primary key but in our project we don't need to track every single interaction but we just need to add the first record into it. Please let me know if there are any challenges with it.
I am not sure why you need to change this.what is the issue you want to address by this change. It feel like a big customisation.
how did you get duplicate entries in IH table, I assume the fact id is system generated.
There are also a backing Pega class structure for the IH tables (fact and dimensions), (Data-Decision-IH-*), the keys will also be set there.
Also since IH is one of the core functionality of Decisioning, there might be other strategic applications (like Pega Marketing )that would utilise IH for their own functionality, hence I feel changing this has wider impact, might cause a issues when you upgrade, or install a strategic application in future.
wrt to your tracking comment, "but in our project we don't need to track every single interaction but we just need to add the first record into it.". Are you planning to discard the later responses?
Every response has a time factor associated to it, finding the latest customer response, i guess is very crucial to business logic.