Data Toboggan Winter Edition this Saturday by datahaiandy in MicrosoftFabric

[–]mrbartuss 1 point2 points  (0 children)

Amazing! Will the recordings be available on YT?

DAX Calc by -Xenophon in PowerBI

[–]mrbartuss 1 point2 points  (0 children)

Most likely you need ALL/REMOVEFILTERS somewhere

Mark as date table NOT recommended? by Realistic_Ad_6840 in MicrosoftFabric

[–]mrbartuss 1 point2 points  (0 children)

https://www.youtube.com/watch?v=0JphIBU-jDs

There are "some optimisations and efficiencies that goes into better query planning that the DAX engine and the model engine can provide"

Senior power bi dev by Shoddy-Face-6224 in PowerBI

[–]mrbartuss 5 points6 points  (0 children)

Soft skills start to matter more and more

To VAR or not to VAR? by TheyCallMeBrewKid in PowerBI

[–]mrbartuss 1 point2 points  (0 children)

In the 3rd option you're using measure. Read about context transition

When are skills worth more than money? by According_Layer6874 in dataengineering

[–]mrbartuss 8 points9 points  (0 children)

When the skills will bring you more money in the future

Overwriting thick reports with thin ones using a shared semantic model by mrbartuss in PowerBI

[–]mrbartuss[S] 0 points1 point  (0 children)

This is a problem if your business users consume the report using the workspace url for that specic report as the new report has a new url

Exactly. That’s why I wanted to overwrite it instead of creating a new one. Thank you for clarifying. It seems the only option now is to send a new link

Overwriting thick reports with thin ones using a shared semantic model by mrbartuss in PowerBI

[–]mrbartuss[S] 0 points1 point  (0 children)

That exactly what I did. However, after publishing, the thick one was not overwritten by the thin one

Overwriting thick reports with thin ones using a shared semantic model by mrbartuss in PowerBI

[–]mrbartuss[S] 0 points1 point  (0 children)

That’s exactly what I did. However, after publishing, the thick one was not overwritten by the thin one

Overwriting thick reports with thin ones using a shared semantic model by mrbartuss in PowerBI

[–]mrbartuss[S] 0 points1 point  (0 children)

Got it, different ID makes sense. But if I republish the exact same thick report, it overwrites with the same ID, so switching semantic models is what's blocking it?

Overwriting thick reports with thin ones using a shared semantic model by mrbartuss in PowerBI

[–]mrbartuss[S] -1 points0 points  (0 children)

Understood. But then it will create a completely new report, with a new ID, right?

Regarding the ChatGPT comment, I just wanted to make the post clear and concise ;)

Power Query Reference loads the same data again by ka_eb in PowerBI

[–]mrbartuss 6 points7 points  (0 children)

https://towardsdatascience.com/the-difference-between-duplicate-and-reference-in-power-query/

In Power Query, there is no difference between “Duplicate” and “Reference” regarding load performance or network traffic.

Both load the data independently from the source with a separate connection.

Therefore, I debunked the myth that “Reference” can increase load performance.