The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Limited relationships are dangerous in Power BI. They come with some unexpected behaviours, and can lead to incorrect numbers on the reporting side. Without knowingly managing them, it can happen that you publish a report and have incorrect summarized values in your visuals.
In this video we demonstrate what the impact of a limited relationship is on your data, and how to easily mitigate the risk and solve the problems at hand.
Furthermore, we have a look at the new directlake connection, and how it seems to be a limited relationship, when in fact it does not behave the same way as a mixed mode model that has a limited relationship.
Directlake still has limitations, and it is not possible to mix directlake connection with import mode or direct query. There are difficult technological challenges underneath the hood - with directlake the vertipaq engine does not translate the queries into the local columnar storage format, but can read Delta Parquet directly. With import mode and direct query, however, queries are sent in SQL to the source, and data is stored in the local vertipaq columnar storage format.
I hope you enjoy the video, and the quick insights into limited relationships, and the challenges they can bring.
from @Poweraegg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.