In this case, what's the primary key in the resulting DE? As it's one to many relationship, the customer id is repeated and the order id is null in some records. Thanks!
It is not always necessary that you must have a primary key - you need to evaluate how you would be using the data. If you expect that the customer record should be unique in a DE, then yes you need a unique identifier like customer id as PK. But lets say you are using a DE for Journey entry where the customer may reenter multiple times - setting a primary key in such cases will cause the reentries to fail. A PK is not mandatory for a DE but need to be used appropriately based on the scenarios where the data will be used
Yes I heard that is being pulled out as there is no one maintaining it any more. Haven't seen any new one yet but some of the community experts may come up with one soon 😊
Oh btw it is still available but the link is private - and not supported if theres any issues. So you may install and use at your own risk - appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FP3yFUAT
Its very helpful. I have a question. When we use data views to query the 6 months data if the data is huge, our queries keep failing. Could you please suggest how to avoid this?
