We have our customized Marketing Customer Data class, which still utilizes the CustomerID as the primary key. We are looking to leverage the OOTB Import functionality with some customizations. As per our requirements CustomerID has to be auto generated and the Users will not be able to import them as part of the excel. So we need extension points to remove the validation of the csv file which mandates CustomerID in the list and we also need an externsion point where the id can be auto-generated.
We were able to find one such extension point pyPreProcessRecordOnImport which can be overridden in the Customer class, but calling this property automatically adds fields like pxUpdateOperator and pxUpdateSystemID which is not part of the customer data structure.
Any suggestions on how to implement above customization is appreciated.
pyPreProcessRecordOnImport is the right activity for extension. The unique ID generation changes could be added here. Is there an explicit Save handled in the extension point? Please explain the steps.
Thanks for your response. Based on my analysis customizing above activity sets the flag .pyIsPreProcessActivityOverriden to true in the data import flow, which in turn invokes the Final Activity pzSavePageRecord. This is where Pega adds some of the OOTB properties that I've mentioned in the list but they are not a part of the Marketing Customer Data Structure. Also can you please suggest if this is the right place to do our custom duplicate validations as well?