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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
srlabhe123
Post Patron
Post Patron

Merging Common Dimensions

Hi All,

  • I am going through a very rare scenario where I have 2 Datasets built from dataflow. The datasets names are DS1 and DS2 which are Direct Query based
  • Now I wanted to design a report based on these 2 Datasets pulling measures form both the datasets
  • The common dimension between these 2 datasets is a Date
  • The measures I wanted to pull are DS1->Customer Count and DS2->No Of Orders
  • I have tried pulling these measures in separate visuals and works fine, but when I try to join the common Dimension from 2 datastest and try creating a measure like ATP= Divide(Customer Count, No Of Orders) it throws invalid output
  • Also if I try to use use it in Metrics having common dimension DS1.Date as column and put ATP an values, it does not give me right data
  • Also the report loads data very slow which is not good user experience at all

Questions :- 

Whether joining common dimensions from 2 Direct Query Datasets based on Dataflow is right approach here?

Also what is best approach to achive right result here ?

Suggestions are welcome, also dont wanted to go with Import as data has millions of records in DS2

 

We are tryting to create environment for users where they can do these by their own and generate reports.

 

Suggestions are appreciated here.

 

1 ACCEPTED SOLUTION
ebeery
Solution Sage
Solution Sage

My recommendations:

  • Use a central date dimension table, where the "date key" is related to both DS1 and DS2 with 1-n relationships
  • To improve report performance, use Import mode.  "millions" of rows does not really justify using DirectQuery in my opinion.  Import mode should be able to handle millions of rows with no issues, as long as you are disciplined about the number of columns and data types you are importing.

View solution in original post

3 REPLIES 3
ebeery
Solution Sage
Solution Sage

My recommendations:

  • Use a central date dimension table, where the "date key" is related to both DS1 and DS2 with 1-n relationships
  • To improve report performance, use Import mode.  "millions" of rows does not really justify using DirectQuery in my opinion.  Import mode should be able to handle millions of rows with no issues, as long as you are disciplined about the number of columns and data types you are importing.
ebeery
Solution Sage
Solution Sage

@srlabhe123 having more info about your model (or a screenshot of the diagram) would be helpful.

Are you using a central date dimension table or are you directly relating between the two tables?  If the latter, what is the cardinality of that relationship?

I am directly relating between 2 tables with cardinality 1-n

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.