Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
kaarel
Resolver I
Resolver I

Mobile Reports SQL 2016 vs. Power BI - duplicate values table relationship

Hi,

 

I've tried to add budget table and sales table to Power BI model, but can't create a relationship using product key, since both got duplicates in them. However, in Mobile Reports SQL 2016 there is no problem. Filtering works, whichever table's product key I use.

 

I know about star schema, how to do it correctly in Power BI etc. I'm just curious why Microsoft has taken 2 different approaches between similar products...

 

For a regular user, it would be much easier, not to think about the dimension tables at all.

 

Cheers,
Kaarel.

1 ACCEPTED SOLUTION
Anonymous
Not applicable

@kaarel Similiar that they both have the ability to create reports, but outside that these are vastly different tools.

Power BI leverages the same technologies used in SSAS Tabular models...essentially they are the same. This allows you to consume a much larger set of data to see everything, not just small snapshots, so it requires that you follow the current capabilities and rules in building that model.

 

Different tools for different aspects of your data and reporting needs.

 

You sound like you have already figured out the solution of just creating a dimension with a unique list of product keys and any metadata. You can than create a relationship from that unique dim to both the tables.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

@kaarel Similiar that they both have the ability to create reports, but outside that these are vastly different tools.

Power BI leverages the same technologies used in SSAS Tabular models...essentially they are the same. This allows you to consume a much larger set of data to see everything, not just small snapshots, so it requires that you follow the current capabilities and rules in building that model.

 

Different tools for different aspects of your data and reporting needs.

 

You sound like you have already figured out the solution of just creating a dimension with a unique list of product keys and any metadata. You can than create a relationship from that unique dim to both the tables.

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.