Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi,
I'm trying to build a sales data dashoboard with data that comes from our data warehouse. The issue i have is that we have multiple shopify stores. Therefore i have multiple sales tables, customer tables etc. Does anyone know the best way to model this in order to give total sales etc.
Any help would be much appreciated.
Solved! Go to Solution.
Hi @Jameswh91 ,
You're aiming to build a STAR SCHEMA model, where each of your sales tables are FACT tables, and you relate these to DIMENSION tables that hold descriptive fields that are common to all the sales tables.
https://docs.microsoft.com/en-us/power-bi/guidance/star-schema
This is standard best practice in almost any (relational) data modelling scenario.
Here's a simplified view of a model I'm currently working on that uses a star schema model over multiple fact tables. You'll see that every dimension table is related to every fact table on common fields:
The actual model has 6 fact tables and 9 dimension tables, but all the fact tables are controllable for calculation purposes by the dimension tables.
Pete
Proud to be a Datanaut!
Hi @Revokez , you can also look into existing third-party connectors. This ready-to-use solution offers a free Shopify Power BI template that already includes the key Shopify tables and built-in data relationships, so you can plug in your data and get started right away: https://vidi-corp.com/shopify-analytics-dashboards/. This template also allows to export data from multiple Shopify stores.
It’s a great shortcut if you’re not familiar with Shopify data modeling or want to speed up the process. Alternatively, you can also look into existing third-party connectors.
Hi @Jameswh91 ,
You're aiming to build a STAR SCHEMA model, where each of your sales tables are FACT tables, and you relate these to DIMENSION tables that hold descriptive fields that are common to all the sales tables.
https://docs.microsoft.com/en-us/power-bi/guidance/star-schema
This is standard best practice in almost any (relational) data modelling scenario.
Here's a simplified view of a model I'm currently working on that uses a star schema model over multiple fact tables. You'll see that every dimension table is related to every fact table on common fields:
The actual model has 6 fact tables and 9 dimension tables, but all the fact tables are controllable for calculation purposes by the dimension tables.
Pete
Proud to be a Datanaut!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 6 | |
| 6 | |
| 5 |