Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
As a test with Fabric, I wanted to make a Paginated Reporting with Power BI Report Builder on a Warehouse (WH) in Fabric, where I have stored some tables of the AdventureWorks DWH DB.
In the Fabric WH, I defined the relations between the tables, like this:
Hi @maartenvanreek ,
I'm sorry I wasn't able to reproduce your situation. Can you provide some details or screenshots so that we can help you better?
And about "NOT ENFORCED", enforced unique constraints are not supported in Azure SQL Data Warehouse. To create an unenforced unique constraints you must include the NOT ENFORCED as part of your statement.
I guess these documents may help you:
https://stackoverflow.com/questions/49941101/how-to-set-any-column-as-primary-key-in-azure-sql-data-warehouse
https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints
Best Regards,
Dino Tao
hi Dino Tao, thanks for your answer, I include 2 screenshots :
-1: Adv.Works (Azure) SQL DB with a relation between 2 tables
-2: Report that selects fields from these 2 tables, in which join is automatically detected. This does not happen if the DB tables are in Fabric (-warehouse) although the PK/FK-relations are defined (but not enforced)
--1
--2
--
I wonder if this issue would not appear if it was possible to create a enforced PK/FK-relation in a Fabric warehouse?
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.