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?
![[FULL EP.16] เซียนพาลุย "เผือก-ฟรอยด์" กรี๊ดลั่น จนปูหนี | เฮ็ดอย่างเซียนหรั่ง | One Playground](http://i.ytimg.com/vi/FsqUvwS3b-Y/mqdefault.jpg)
MUITO OBRIGADA!!!!!! Me ajudou muito
This is very useful
Thank you very much, this is very useful
Hi, Thank you for sharing this.very helpful to me.
Can you Please upload more complex SQL queries using Journey Builder Automation. As well as can you teach me synchronized DataExtension Automation.
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
@@sfmctrailblazers Awesome, thanks for the explanation.
Hello. Thank you for this! I can't see the Query Studio in AppExchange anymore. Do you have an alternative one for it?
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
Thanks again!
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?
Try breaking the queries into smaller durations instead of trying to get all 6 months in one shot
I can't see the screen clearly please fix it