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,
Last year, we started rolling out a new ERP system that's fundamentally different from our old one.
Previously, when combining multiple sources, i would try to align the structure of the SQL query and append/union them.
Now I'm trying to use separate fact tables but with common dimensions, but i'm running into trouble when a dimension exists in the new software, but not in the old one.
I've simplified it in an example, where the "region" dimension was not available in the old software:
My two fact tables look like this
My relationships like this
I created 3 measures:
Turnover old software = SUM('Old software'[Turnover])
Turnover new software = SUM('new software'[Turnover])
Turnover overall = Turnover old software + Turnover new software
Now, when i create a table that attributes the overall turnover to the regions i would expect something like this
| Year | Region | Turnover overall |
| 2021 | Blank | 5.000.000 |
| 2022 | Blank | 6.000.000 |
| 2023 | Blank | 7.500.000 |
| 2023 | Europe | 1.200.000 |
| 2023 | USA | 3.000.000 |
Since it can't attribute the turnover from the old software to a region, it should create a blank category.
But instead, it's adding the turnover it can't attribute to each category, like this:
Is this expected behaviour? If so, can you help me understand why?
Is there a solution?
Thank you!
Solved! Go to Solution.
Hi @EmilePl ,
Based on my test results, it seems that this behaviour may occur because of automatic aggregation of processed data
When you join the region it will give him an equal share of the turnover depending on the date.
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @EmilePl ,
Based on my test results, it seems that this behaviour may occur because of automatic aggregation of processed data
When you join the region it will give him an equal share of the turnover depending on the date.
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
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 |
|---|---|
| 51 | |
| 37 | |
| 35 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 72 | |
| 70 | |
| 39 | |
| 34 | |
| 23 |