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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello everyone,
I’m encountering a cardinality issue in my Power BI model and would appreciate your help.
I’m working with an Excel file that contains a list of applications, with one sheet per month. This file is stored on SharePoint, and I’ve connected it to Power BI to visualize the number of applications on a monthly basis. The issue I’m facing is due to duplicates, as some applications are listed in multiple months. I don’t want to overwrite these duplicates, but it’s creating a cardinality problem in my data model.
Here’s my setup:
- I have a Source table that contains an INS column (application number) for incidents related to applications.
- I’m trying to create a "many-to-one" relationship between this table and my Application table via the INS column, but Power BI is not allowing me to do so.
How can I resolve this issue? I would like to keep the duplicates without causing conflicts in the model. Any advice would be greatly appreciated!
Solved! Go to Solution.
Hello @Anonymous
Based on your above explanation, i hope, you should have proper dimensional model.
1) Create a bridge table to handle the duplicate application numbers.
2)Make sure to have unique value on the INS column in the bridge table to eliminate duplicates.
3) Then, relate the bridge table to both the Applications and Source tables.
This will maintain the necessary relationships without overwriting data.
Hope this helps
Regards
sanalytics
If it is your solution then please like and accept it as solution
@Anonymous One possible solution is to create a bridge table by keeping only unique value (no duplicate). If possible so kindly share the dummy data because it wud be easy to answer your question.
Hello @Anonymous
Based on your above explanation, i hope, you should have proper dimensional model.
1) Create a bridge table to handle the duplicate application numbers.
2)Make sure to have unique value on the INS column in the bridge table to eliminate duplicates.
3) Then, relate the bridge table to both the Applications and Source tables.
This will maintain the necessary relationships without overwriting data.
Hope this helps
Regards
sanalytics
If it is your solution then please like and accept it as solution
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 61 | |
| 59 | |
| 42 | |
| 18 | |
| 15 |
| User | Count |
|---|---|
| 109 | |
| 102 | |
| 39 | |
| 29 | |
| 29 |