I posted this issue before here:
https://learn.microsoft.com/en-us/answers/questions/1434821/in-power-bi-report-builder-in-query-desi...
but I got an answer that this site might be a better place.
NB: I copied/pasted the text from my 'Fabric-ticket' to this ticket, but it did not copy the screenshots, so maybe better to look at the original ticket:
--
I did a test with Fabric (free trial) to see if the Warehouse storage could be a good datasource for Power BI Report Builder. For this test, I used: https://www.mssqltips.com/sqlservertip/7833/microsoft-fabric-build-data-warehouse/
After the data from the AdventureWorksLT2017 DB was loaded in the Fabric-Warehouse, I added PK+FK constraints to define the relationships between hthe tables.
But in Power BI Report Builder, in Query Designer, these relationships were not detected (so the join-columns I had to add myself):
--
PIC-1
--
I also did the same test for this report with the same DB, AdventureWorksLT2017, but now in Azure SQL (where I also had defined the PK/FK fields), and here it worked OK (so PBI-RB detected the relationships):
--
PIC-2
--
Could this be a bug in Power BI Report Builder, or maybe it's not prepared for these new Fabric storage modes ( Warehouse/Lakehouse)?
NB: I know that in Fabric I can create a (semantic) model for the Warehouse and define the relationships here, but these are 'Power BI relationships', not the 'normal' relationships in a relational DB (that don't have a cross-filter direction):
--
PIC3
--
But I don't want to do any analysis with a dashboard (PBIX-report with a semantic model as a source), I just want a simple paginated report that I can print (RDL-report with a (Azure) SQL as a source)
