Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
I am trying to join multiple SQL tables together for a large project. I am currenlty trying to use 6 of those tables to create a table within PBI. The first 3 tables that I add are HCA_Division, Building, & Facility but when i go and add the subtype table i get the following error "Can't determine relationships between the fields". I have worked on fixing relationships and also joined tables via merge but no luck.
I have highlighted the tables that i am using below in my schema. Can anyone see something that i missing.
You've added fields to your visual, but Power BI cannot figure out how to render it because it cannot create a filter path between the various fields. For example, Nothing you add from the Public Subtypes table is going to filter properly because that relationship is inactive. Same with Buildings and Facilities.
FRequencies will go to Groups, then Subtypes, but then it stops.
You really need to try and fix this model to be a Star Schema. Power BI is designed to work with a Star Schema, and you do not have that. This, as well as overly complex DAX, will result.
Microsoft Guidance on Importance of Star Schema
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reporting@edhans Please see updated schema. I have built this star schema off 3 fact tables, Assets, PMs, & Grouped PM. The error is still happening though.
THe model looks good. 👍
I'd need to know more about the fields you are using though. For example, if you use Codes field from the Public Types table and the Building ID from the public PM Groups table, it won't work. There is no filter path connecting those. It would go from Public Types to Public Assets, to Public PMS, but then it would stop. All filters with PUblic PMS are where that is the FACT table and the many side. It will not filter through to Frequencies for example. The filter direction runs from Frequencies to PMS, not the other way.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingYour file link says I don't have permission.
I understand you are only using key fields in your visuals, but not all key fields will reach all other tables. Filtering is one way so everything is not "connected" to each other. Nor should it be by the way. You just have to tweak the model to filter in the directions you need to get the data you need. Typical modeling problem. A good model is half the battle. I go round and round with my own stuff quite often as well.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi @Anonymous ,
It's hard to understnad what you are trying to ask here.
Kindly refer following link to get your question asnwered properly:
https://community.powerbi.com/t5/Community-Blog/How-to-Get-Your-Question-Answered-Quickly/ba-p/38490
Thanks,
Pragati
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 97 | |
| 71 | |
| 50 | |
| 47 | |
| 44 |