Absolutely GAME CHANGER for me !!! I've been struggling for a week with calculated table now I cant wait to go back to my project !!Thank you

@PragmaticWorks

Жыл бұрын

Great to hear! Thanks for watching!

You giving me a new job! Thanks again. Old school Excel and VB user. This is sooo much more intuitive. Things have come a long way.

@PragmaticWorks

2 жыл бұрын

Awesome! Glad it helped Patrick - Mitchell Pearson

Great job Mitchell!! really love your videos and really look forward to seeing more examples of data modeling and advanced DAX usages.

Mitchell - That was OUTSTANDING! Great pace and example. Thanks for staying in the "shallow end"!

@PragmaticWorks

3 жыл бұрын

Thanks Tim, glad you enjoyed it!

Fantastic video, this helped me wrap my head around the issue with row context not filtering. Your examples are super clear and I really appreciate the way you keep this accessible even to people from a non-programming background.

@PragmaticWorks

Жыл бұрын

Great to hear!

Thanks for teaching us row context in a simplified way. Looking forward for future videos

@PragmaticWorks

3 жыл бұрын

Glad you liked it!

I found this very helpful. The step-by-step explanation is very good and can be understood very easily. Love to see more videos from you.

@PragmaticWorks

3 жыл бұрын

Thank you! Will do!

If row Context is used active relationships are disabled. How the hell am I just learning this now? Surely this should be Day 1 of every Power BI course! Thx for the vid BTW

I love your teaching style ... Very clear and easy to understand... Thanks a lot

@PragmaticWorks

2 жыл бұрын

Glad to hear that

Excellent presentation Mitchell. You are the best!!! You make complex things seem easy. Thank you so much.

@PragmaticWorks

2 жыл бұрын

Glad you enjoyed!

very clear! much appreciated!

absolutely amazing explanation 👏 glad to have found your channel. keep it up!

Wow, this is fantastic for people trying to learn this. Thank you!

Love your training style. Brilliant!

@PragmaticWorks

2 жыл бұрын

Thank you Patrick, much appreciated! - Mitchell Pearson

Superinteresting video! Looking forward for the next one!

@PragmaticWorks

3 жыл бұрын

Thanks! Glad you enjoyed, definitely more to come!

Mitchell, you are an excellent tutor 👍👍👍👍

Great Explanation.. very helpful. thanks for sharing it.👍👍👍👍

@PragmaticWorks

2 жыл бұрын

Glad you enjoyed it!

Hi! Great video. Very helpfull. The filter contex is always tricky to understand. Very well explained. Wish to see more videos

@PragmaticWorks

3 жыл бұрын

Glad it was helpful!

This was good. Thanks Mitchell.

@PragmaticWorks

3 жыл бұрын

Thanks John!

Excellent teacher!

@PragmaticWorks

3 жыл бұрын

Wow, thank you!

Congratulations on this video. Very clear and informative. Thank you.

@PragmaticWorks

6 ай бұрын

Glad it was helpful! Thanks for learning with us!

Mitchell! what a great explanation. Thanks a lot

@PragmaticWorks

2 жыл бұрын

Glad you enjoyed it!

Best teacher!

@PragmaticWorks

3 жыл бұрын

Wow, thanks! Glad you enjoyed it!

Amazing Job

@PragmaticWorks

3 жыл бұрын

Thanks!

Fantastic explanation Mitchell ! Is there a video on context transition from you?

Thanks a lot !!!

@PragmaticWorks

2 жыл бұрын

You are welcome!

Very useful tips

@PragmaticWorks

3 жыл бұрын

Thanks a lot! -Mitchell Pearson

calculate(MAXX(Sales,Sales[Order Date]),Customer[CustomerKey]) This fuction is work and can be done last order date each customer

Great explanation Sir...

@PragmaticWorks

Жыл бұрын

Thank you!

It's an awesome/fabulous video. Do a video on Power BI Service.

Hi Mitchell, very helpful. Really grateful for your videos. I have question, why you did not use related table in large values table and used related function. Thanks.

Thanks

@PragmaticWorks

2 жыл бұрын

No problem

Nice! When is the next one coming? 🤔

Hi Please provide data set for Practice. why the active relationship get deactivated when we have created the active relation?👀👀

What should I do if I need not the date of the last order, but its ID? I still need to determine, which order was the last, but what I want in the calculated column is not its date, but its ID. I'm stuck.

Hi! Fresh new in Power BI, coming from Apsheet. I have a table where one record's status depends of another record's status. Wrong data model but nothing I ca do about it (client's) Sales and deliveries in the same table One delivery per sale One product per sale Once delivery is complete, Sale will be complete. Dims: Transaction date Delivery place Product For each Sale I am looking to find another record (delivery) with the same TDate, DPlace and Product and return it's status. What formula works similar to Select(Table[Column], AND(conditions))? Thank you!

Sir, I am having the data of sales amount having the column State and District. I have created a measure for total sales. and created 2 Slicer i.e. State and District and I have sync slicer for all the pages of the report. I have created a table with column State and Sale. If I don't selected any slicer from state then default value should be State Column and Sale Column and If I select any state the respective district of the state should come i.e. District column in place of State Column and Sale column. Please advise sir, how it can be done.

Can anyone help me please? Where are the files to download ? I mean the dataset Thank you

where can i get its source file and source code of DAX

Regarding starting at @11:36. ChatGPT is my personal IT tutor. According to Chat, the RELATED function should only be used on the one side of a relationship and never on the many side. Quote: "The information provided by the KZread instructor is not accurate. The DAX RELATED function is specifically designed to be used on the "one" side of a one-to-many relationship. It allows you to retrieve values from the "many" side based on a matching key. If you are on the "many" side of a relationship and the relationship is broken due to a calculated column, using the RELATED function will not fix the issue. In fact, using RELATED in such a scenario may lead to incorrect or unexpected results. To address issues with broken relationships caused by calculated columns on the "many" side, you would typically need to review and modify the calculated column or consider alternative approaches such as using measures or calculated tables. Remember, the RELATED function is used to navigate from the "one" side to the "many" side of a relationship. If the relationship is broken, the RELATED function will not resolve the issue." The following is the question that I asked ChatGPT: A KZread instructor just said that if I am on the many side of a relationship, and the relationship is broken due to the side affect of a Calculated Column, then I can use the RELATED DAX function to fix it. Is this correct? I was told that RELATED should only be used on the "one" side of a one-to-many relationship. The example the KZreadr used is: Product Name = RELATED(‘Product’[English Product Name])

@PragmaticWorks

11 ай бұрын

Hello and thanks for commenting on our video. I have reviewed the video and it is 100% correct and accurate. If you are in the table, on the one side of the relationship, for example a dimension table, related WILL NOT work to return information from the many side of the relationship. Related function only returns a single value and therefore will only work if you are on the many side of the relationship trying to return a single value from the one side. The code examples in the video back up the context provided. Similarly, relatedtable returns a table and therefore, if i'm in a dimension table and want to return a set of related rows from the many side of a relationship, I would use related table, since it can and will return a table expression. - Mitchell Pearson

@statesman6379

11 ай бұрын

@@PragmaticWorks Awesome! Thanks for the clarification. So it seems it doesn't matter which side of the relationship you are on if you are using relatedtable since it returns a table, is this correct?

@PragmaticWorks

11 ай бұрын

​@@statesman6379 Technically Yes, you can use RELATEDTABLE on either side... but relatedtable is more complex to work with because now you have a table expression and you need to perform an operation on that table to return a scalar value. In contrast, the related function will return a scalar value by default and will not require further manipulation and therefore if you are returning a single value from the one side of the relationship RELATED would be ideal. In the video, I probably use a sumx or equivalent type function on top of relatedtable to return a scalar value.

"Row context exist therefore relation is disabled" = no idea why and what does it mean? I see no logic behind this. (this is beginner question:) I don't think the row context is explained here.