Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Hi,
I'm working on a task where the dataset consist of one fact table and four dimension tables, but there is no any common key or foreign keys between the fact table and the dimensions.
Where the task asks for clean data model and two pages report that includes measures depend on the relationship established between the fact and dimensions
How to solve these limitations?
Hi @mohallaham ,
Just checking in to see if your query is resolved and whether the responses shared were helpful. If you are still facing any issues, please feel free to reach out with additional details or sample data so we can assist further.
Thank you.
Hi @mohallaham ,
Thanks for reaching out to Microsoft Fabric Community.
Just wanted to check if the responses shared address your question. They correctly explain the modeling limitation and the valid approaches when a shared business key exists.
If you are still facing issues applying this to your scenario, please share a small sample of the fact and dimension tables along with the expected outcome. That will help confirm whether a clean relationship can be established or if the limitation is with the source data itself.
How to provide sample data in the Power BI Forum - Microsoft Fabric Community
Thank you.
if there is no common key or foreign keys between the fact table and the dimensions, is it possble to combine some column to create a unique one?
could you pls provide some sample data and expected output?
Proud to be a Super User!
If your fact table and dimension tables truly have no shared business key (no ID, code, date, name, etc.), then you cannot build a meaningful relational model in Power BI. Any relationship you create would be artificial and your measures would be unreliable.
If there is no common key between fact and dimension tables, you cannot build a clean data model directly, so you must create one. The correct approach is to derive a surrogate or composite key using common business fields like date, region, product, or category after cleaning and standardising the data in Power Query. If the relationship is many-to-many, a bridge table can be used. Without establishing a relationship, dimension-based measures will not work properly in the report.
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 61 | |
| 43 | |
| 30 | |
| 26 | |
| 23 |
| User | Count |
|---|---|
| 135 | |
| 114 | |
| 58 | |
| 39 | |
| 35 |