Need to map a customer class with only one primary key. This is the default pega marketing behavior.
But our customers data is coming from external table with two keys.
Question: What happens if we create database view(materialized) and concatenate (key1+key2 ---> CustomerID column of the data base view)? We cannot have a primary key on a view, but we can have a class key to our customer class. Does it work in pega marketing? Before we start a poc, just wanted to know if there any design limitations with this approach. Please feel free to suggest any alternative approache as well. Thanks in advance.
Yes this will logically work. The only thing I'd be concerned about is performance impact. Many things are indexed off of the customer key. Having a concatenated field in the view will likely not use the indexes, so this will need to be validated.
Thanks Saleem_A. I am just trying to understand about the performance impact. Technically pega needs to get the customer snapshot details only when the ADM model needs to run(In delay learning response) and to calculate propensity while making a decision. At this point, customerId(concatenated column) will fetch the record and feed the predictors values to the learning model from the customer table. Please help me to understand on the indexes which are created. Thanks in advance.