I love it! The nice part of your videos is you have ideas that they are simple to implement in different use cases. I will use that on Monday 😀 Thanks!

@CurbalEN

2 ай бұрын

This was not my idea, i was asked about it but thanks!! :)

I LOOOOOVE the return of DAX Fridays! 🎉

@CurbalEN

2 ай бұрын

❤️❤️

Great video for morning cofe ;). Thank You.

Hi Curbal, Great tutorial, thank you for sharing it

The DAX approach to creating a dynamic slicer is clever, especially the workaround using COUNTROWS to handle multiple selections smoothly. It would be interesting to know the performance implications of this method on larger datasets.

@CurbalEN

2 ай бұрын

Let us know if you test it in bigger datasets!

It's great. Maybe I would try to solve it from the source and/or model first, so that the DAX measure is not complicated, but if the business context does not allow it, this advice is excellent.

WoW..WoW..WoW.. @Ruth.. This is just 👌👌😀 Just ♥ this.

@CurbalEN

2 ай бұрын

😃

Cool.Nice tips ....

Thank you

Thank you so much for the content you have been posting on KZread Channel. May I suggest/ask something? Can you please teach us how to create a multilanguage Dashboard in Power BI? I have been looking for something on Google, and KZread and so far I couldn't find anything. Please, can you help me with this? Thank you

This is great! I actually JUST ran into a similar issue, but instead of OR when selecting values, I need it to be AND. Curious what your thoughts on adjusting the DAX to account for AND instead of OR.

1:05, a question if I may? why not use advanced option and simply split it to rows? it will then automatically create 1 column table.

@CurbalEN

2 ай бұрын

Sometimes you need the data as is. Think ot was complete sentences from a questionnaire instead, you dont want to split them right?

@ExcelInstructor

2 ай бұрын

@@CurbalEN ok, let me try asking other way around. You took your original table, made a reference to it, then you extracted unique values after splitting the text in the column. Your way was to split it to another column and then combined the columns into 1 column and extracted the unique values. So what Im asking is - why do it the long way around, when column split function can split it diresctly into rows, so trying to fast recreate this: let Source = Excel.CurrentWorkbook(){[Name="name"]}[Content], #"Split Column by Delimiter" = Table.SplitColumn(Source, "Column1", Splitter.SplitTextByDelimiter(",", QuoteStyle.Csv), {"Column1.1", "Column1.2"}), #"Unpivoted Columns" = Table.UnpivotOtherColumns(#"Split Column by Delimiter", {}, "Attribute", "Value"), #"Removed Other Columns" = Table.SelectColumns(#"Unpivoted Columns",{"Value"}), #"Removed Duplicates" = Table.Distinct(#"Removed Other Columns") in #"Removed Duplicates" this is mostly what you did. so if you would @ 1:04 opened the advanced options, you would see option to split into rows, so basicly this: #"Split Column by Delimiter" = Table.SplitColumn(Source, "Column1", Splitter.SplitTextByDelimiter(",", QuoteStyle.Csv), {"Column1.1", "Column1.2"}), #"Unpivoted Columns" = Table.UnpivotOtherColumns(#"Split Column by Delimiter", {}, "Attribute", "Value"), #"Removed Other Columns" = Table.SelectColumns(#"Unpivoted Columns",{"Value"}), would be replaced with just this: = Table.ExpandListColumn(Table.TransformColumns(Source, {{"Column1", Splitter.SplitTextByDelimiter(",", QuoteStyle.Csv), let itemType = (type nullable text) meta [Serialized.Text = true] in type {itemType}}}), "Column1")