3 things you need to watch out for, in Power BI

preview_player
Показать описание
In three instances last week, I thought that either I was going mad or blind or there was something wrong with Power BI. It turns out that it was 50-50. Let me show you so you dont go mad too!

Chapters:
00:20 Issues with what-if parameters
00:00 Sync a what if parameter with a new tab
04:30 Power query is case sensitive, DAX is not


SUBSCRIBE to learn more about Power and Excel BI!

Our PLAYLISTS:

☼☼☼☼☼☼☼☼☼☼

POWER BI COURSES:

Want to learn Power BI? How about you take one of our courses? Here you can find the available courses:

☼☼☼☼☼☼☼☼☼☼

ABOUT CURBAL:

▼▼▼▼▼▼▼▼▼▼

If you feel that any of the videos, downloads, blog posts that I have created have been useful to you and you want to help me keep on going, here you can do a small donation to support my work and keep the channel running:


Many thanks in advance!

▲▲▲▲▲▲▲▲▲▲


************





************


QUESTIONS? COMMENTS? SUGGESTIONS? You’ll find me here:
Twitter ► @curbalen, @ruthpozuelo

#CURBAL #SUBSCRIBE
Рекомендации по теме
Комментарии
Автор

I found a couple of workarounds for the slicer issue.
1) Change slicer type to "Between" instead of "Single" and set min & max as the same number. This would work if you're the only one using the report.

2) This way is a bit better and cleaner. Change slicer type to "Greater than or equal to" and change the measure from "SELECTEDVALUE" to "MIN". Hide the slider and resize the slider till the upper limit input box is hidden (it will be grayed out anyways). Now if you enter any value in the lower limit box, it will be taken without sampling.

I tested both methods on 100K series and both worked fine.

YazanWael
Автор

That Power Query case was new to me, thanks for this!

SolutionsAbroad
Автор

didn't know this....thanks 4 sharing Ruth!

PedroCabraldaCamara
Автор

Hola Ruth, definitivamente todos tus vídeos son interesantes. Te admiro 😊.

Tutoliber
Автор

Seems like the limit is ~1000 values for the parameter slicer. You can see how it samples the source values when you choose "Show as a table" ... slicer option.

SteelLanRat
Автор

It's nice, i used the same example for a one dashboard, and i have the same problems with a LowerCase and UpperCase, Thanks for the video you ROCK!

marcusandrade
Автор

I solved syn slicer issue JUST BEFORE watching this video. I have to say your video is really useful!

张泽文-qr
Автор

Hi, what would be the best way to change the underlying data souce in a report from excel files to tables from a database when the column names are not the same? Any best practices here? Thanks

DanielWeikert
Автор

Thanks Ruth - that parameter issues has been driving me crazy -Glad to know I'm not the only one!

stevemorgan
Автор

Thx ruth, number 4 ??

have problems with variables. If i build a variable, in a measure, excactly as a measure, it gives me another result when i use an outside measure which is excactly the same as the variable. Bug??

frankgovers
Автор

Hahaha... Thanks Ruth, this is the one I talked to my colleague yesterday. Thanks again for your sharing. Very good one.

dannyhometown
Автор

I had the same issue with parameter selection and couldn't understand why it was behaving like this. As regards entering data manually, i think PBI like consistency in a column

vida
Автор

The third example where you created a table with 4 instances of your name, my guess is probably Microsoft may have set up as a distinct by default so as to allow for measures to aggregate. Also, it's good that you pointed out that its not case sensitive.

rayng
Автор

I'm guessing that the last issue is caused by the compression for the columnar db. It reads the first value and whenever it finds an equivalent value (ignoring case) it will point to the first one.

YazanWael
Автор

🤯 and also 😒... That's so quirky it's annoying...
I would have gone crazy if I had run into this before watching this!
Thanks for bringing this to our attention, Ruth!

HachiAdachi
Автор

Muy interesante como es el comportamiento y útil . Saludos Ruth

joseagundis
Автор

Wow...you took one for the team Ruth...actually you took 3 :P...much appreciated! :)

cleanthisconstantinou
Автор

50/50 that this is an excellent video!!

oliveroshea
Автор

Ohhh gosh I've already had the problem with the sampling!! It was horrible haha.
In the end, we just came up creating some more parameters for the decimal, centesimal, thousand parts...
That worked buuuut in the backend we ended up having many parameter tables to manage

joaoluismartins
Автор

the way it behave is correct, actually having a huge series with small increments has no sense, rest is pretty logic too . thanks for sharing

mmtindaro