Alberto, I find your content very accurate and meaningful. Respect from the bottom of my heart. You are a Maestro. I have learnt a lot from your videos. I cannot afford your courses but access to the free videos on TH-cam are helping me a lot. Thanks for such a series of wonderful videos.
I may not be able to thank you everyday but i am trully grateful everytime i watch your videos.these learning gems are easy to watch i mean i dont get intimidated why I don't understand because i knew you will double down on the concept. Bless you sir.
Thank you, I always thought in (weak) limited relationships both RELATED() and RELATEDTABLE() does not work. This video helps but also makes me think which other DAX functions works (and do not work) in limited relationships.
Great video, finally understanding the use of RELATEDTABLE() function. However, I've got a question on this one. What is difference between using CONTROWS ( RELATEDTABLE (SALES) ) and applying Context Transition CALCULATE ( COUNTROWS (SALES) ). I suppose both would generate the same result/values. Is there any performance impact?
Great video as always! I have a question: Considering the following DAX queries A: EVALUATE ADDCOLUMNS ( SUMMARIZE ( 'Product', 'Product'[ProductSubcategoryKey] ), "Subcategory", RELATED ( ProductSubcategory[ProductSubcategory] ) ) B: EVALUATE ADDCOLUMNS ( 'Product', "Subcategory", RELATED ( ProductSubcategory[ProductSubcategory] ) ) Why does query A doesn't work while query B works? What does the SUMMARIZE (or SELECTCOLUMNS for that matter) do that it causes the RELATED function to stop working?
Query A performs a GROUPBY and the result is not a row in Product, but a value in Product[ProductSubcategoryKey]. Because RELATED is a function that "unlocks" the access to the expanded table (which is an internal implementation detail), when the row context is not on Product, you do not have access to the expanded table. The result of SUMMARIZE / SUMMARIZECOLUMNS is never a table that has relationships in the model, it's always a table that still keeps the data lineage of the columns, but cannot leverage model relationships.
I love the data formatting in Power BI. It's the easiest and the most dangerous thing. if you know what are you doing it took only 1 min but only one mistake can collapse all your data.
A question out of this topic, is there any way to retrieve the historical refreshes that occurred on the SSAS Tabular model (something like refresh history in PBI Premium datasets)? Thanks in advance for your guidance.
*NEW COLUMNS* 3:00- RELATED 4:30- IF(RELATED) 6:00- demonstration on how RELATED doesn't work with a limited relationship 8:30- COUNTROWS(RELATEDTABLE) 10:39- AVERAGEX(RELATEDTABLE) 12:40- AVERAGEX(ALLNOBLANKROW)...COUNTROWS(RELATEDTABLE) *NEW MEASURES* 14:50- SUMX(COUNTROWS(RELATEDTABLE))
Alberto, I find your content very accurate and meaningful. Respect from the bottom of my heart. You are a Maestro. I have learnt a lot from your videos. I cannot afford your courses but access to the free videos on TH-cam are helping me a lot. Thanks for such a series of wonderful videos.
I am learning BI, but I've got enough confident only after watching your tutorials, A Big thank You Alberto :)
this man is amazing.
he never gets tired of this.
I may not be able to thank you everyday but i am trully grateful everytime i watch your videos.these learning gems are easy to watch i mean i dont get intimidated why I don't understand because i knew you will double down on the concept. Bless you sir.
Your explanations are always on another level!
Always waiting for your next video...a new DAX learner, your videos give so in depth knowledge... Thanks 🙏👍
Thank you, Alberto. I had a RELATED problem just last week. This is so helpful.
Excellent explanation, clear and easy to understand.
Thank you, I always thought in (weak) limited relationships both RELATED() and RELATEDTABLE() does not work. This video helps but also makes me think which other DAX functions works (and do not work) in limited relationships.
Excellent explication, Alberto. Thanks so much.
Thanks Alberto for your easy explanation
Great video, finally understanding the use of RELATEDTABLE() function. However, I've got a question on this one.
What is difference between using CONTROWS ( RELATEDTABLE (SALES) ) and applying Context Transition CALCULATE ( COUNTROWS (SALES) ). I suppose both would generate the same result/values. Is there any performance impact?
They are identical, same result, same performance.
Thanks for this great video Alberto. Can you talk more on the Island you talked about when explaining limited and strong relationship. Thanks
See this: www.sqlbi.com/articles/strong-and-weak-relationships-in-power-bi/
From all of my heart, thank you ❤️
2:02 - RELATED
-- creates a calculated column in Sales (Many) and accesses a column in Product (One)
7:41- RELATEDTABLE
Thanks for the video. This is very useful to know.
Well explained professor! Thanks and keep bringing it up
from which resource do u study? u r amazing. your teaching skills r amazing..
Excelent. Practical. Real use cases.
Expaining what works and what do not work?
I´d like to get the same in spanish 😀
Great video as always!
I have a question:
Considering the following DAX queries
A: EVALUATE ADDCOLUMNS ( SUMMARIZE ( 'Product', 'Product'[ProductSubcategoryKey] ), "Subcategory", RELATED ( ProductSubcategory[ProductSubcategory] ) )
B: EVALUATE ADDCOLUMNS ( 'Product', "Subcategory", RELATED ( ProductSubcategory[ProductSubcategory] ) )
Why does query A doesn't work while query B works?
What does the SUMMARIZE (or SELECTCOLUMNS for that matter) do that it causes the RELATED function to stop working?
Query A performs a GROUPBY and the result is not a row in Product, but a value in Product[ProductSubcategoryKey]. Because RELATED is a function that "unlocks" the access to the expanded table (which is an internal implementation detail), when the row context is not on Product, you do not have access to the expanded table. The result of SUMMARIZE / SUMMARIZECOLUMNS is never a table that has relationships in the model, it's always a table that still keeps the data lineage of the columns, but cannot leverage model relationships.
Can Related function get the "Text value" from the related dimension table? If yes, please show an example. TIA
I love the data formatting in Power BI.
It's the easiest and the most dangerous thing.
if you know what are you doing it took only 1 min
but only one mistake can collapse all your data.
Are there any scenarios when we need not use RELATED and RELATEDTABLE functions to access column from another table?
Finished watching
A question out of this topic, is there any way to retrieve the historical refreshes that occurred on the SSAS Tabular model (something like refresh history in PBI Premium datasets)? Thanks in advance for your guidance.
Masterstroke 💯👌👌🦸♂️
But for limited relationships we need a refresh of the dataset to get the data from Direct query
LOOKUPVALUE also doesn't work with a limited relationship, in my experience.
Yes, RELATED only works with regular relationships.
and who knows that in Tableau has a similar function or it's easy with their Tableau SQL motor?
The catch cry “enjoy DAX” is only possible because of SQLBI
DAX = RELATED (SQLBI)
Can you provide the data sets user please. so that we can practice it properly..plzz 🙏
Follow the link in the description!
Hello. How do you increase the font size of the formula bar easily?
Ctrl+MouseWheel
ctrl++
Man🔥🔥👍
Maybe RELATED should be renamed RELATEDVALUE so it is clearer.?
wrong E-R schema, because ProductDQ should be connected to Product table, not to Sales table.
*NEW COLUMNS*
3:00- RELATED
4:30- IF(RELATED)
6:00- demonstration on how RELATED doesn't work with a limited relationship
8:30- COUNTROWS(RELATEDTABLE)
10:39- AVERAGEX(RELATEDTABLE)
12:40- AVERAGEX(ALLNOBLANKROW)...COUNTROWS(RELATEDTABLE)
*NEW MEASURES*
14:50- SUMX(COUNTROWS(RELATEDTABLE))