How are you getting (Berlin - DE, UK, TN) ?
The combination you need to look at is row wise
B has Berlin - DE (row number 2) and D has Berlin - DE (row number 4) hence both are 0
Now if you keep looking row wise you will get unique value for the combination of City and Country and hence C has Berlin -NH hence 1, F has Bristol- TN hence 2, etc... only repetition was B and D as mentioned above.
Hi @abhinav.singa11,
it is important to know that The number that gets assigned to each unique tuple of city and country does not follow a particular pattern, if the combination is unique so it will get a unique number , if not like the Berlin-DE combination we get a repeated 0, that's why to get the distinct number of combination of city and country they used
COUNT ( DISTINCT UNIQUE_ID ( "Vendors"."City" , "Vendors"."Country" ) ) on the documentation
How are you getting (Berlin - DE, UK, TN) ?
The combination you need to look at is row wise
B has Berlin - DE (row number 2) and D has Berlin - DE (row number 4) hence both are 0
Now if you keep looking row wise you will get unique value for the combination of City and Country and hence C has Berlin -NH hence 1, F has Bristol- TN hence 2, etc... only repetition was B and D as mentioned above.
Hi Abhishek,
Thnk you for the explanation and correction
Hi @abhinav.singa11,
it is important to know that The number that gets assigned to each unique tuple of city and country does not follow a particular pattern, if the combination is unique so it will get a unique number , if not like the Berlin-DE combination we get a repeated 0, that's why to get the distinct number of combination of city and country they used
COUNT ( DISTINCT UNIQUE_ID ( "Vendors"."City" , "Vendors"."Country" ) ) on the documentation
Hi Rashid,
Thank you for the explanation