You say "joins" a lot but it seems like you mean "relationships" vs "blending"? Joins are done in the physical layer, while relationships are in the logical layer.
In one data source I have Order ID as String. The other data source has Order Identification with the same information so they should automatically be linked right? They were not linked. Order Identification came over as a Measure so I changed it to a dimension. Then I had to change the data type from # to ABC. So at this point, how can I force a relationship between Order ID in one data source and Order Identification in the other data source?
Best explanation so far in the concepts
simple and effective video .great job done, Thanks
Simple and effective explanation. Can you show practically ,when we use the joining how it creates the duplicate records? Thanks!
Thanks for the demo & explanations. Request to share datasets, other than Sample Superstore for practice.
You say "joins" a lot but it seems like you mean "relationships" vs "blending"? Joins are done in the physical layer, while relationships are in the logical layer.
Relationship is the right term for that. Thanks
Easily understood...thanks
In one data source I have Order ID as String. The other data source has Order Identification with the same information so they should automatically be linked right? They were not linked. Order Identification came over as a Measure so I changed it to a dimension. Then I had to change the data type from # to ABC.
So at this point, how can I force a relationship between Order ID in one data source and Order Identification in the other data source?
If you can do it at data source level..try to perform cross database join/Join, else data blending is the option.
why only left join can we perform while blending ?
Hi can u explain difference between cross database join and data blending
Thank you sir