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

We'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

Reply
EmilePl
Frequent Visitor

Trying to combine old and new software

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

screenshot 1.png

 

 

 

 


My relationships like this

screenshot 2.png

 

 

 

 

 

 

 

 

 

 

 

 

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

YearRegionTurnover overall
2021Blank5.000.000
2022Blank6.000.000
2023Blank7.500.000
2023Europe1.200.000
2023USA3.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:

screenshot 3.png

 

 

 

 

 

 

 

 

 

Is this expected behaviour? If so, can you help me understand why?
Is there a solution?

Thank you!

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @EmilePl ,

Based on my test results, it seems that this behaviour may occur because of automatic aggregation of processed data

vxiandatmsft_0-1712887714435.pngvxiandatmsft_1-1712887725828.png

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.

 

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Hi @EmilePl ,

Based on my test results, it seems that this behaviour may occur because of automatic aggregation of processed data

vxiandatmsft_0-1712887714435.pngvxiandatmsft_1-1712887725828.png

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.

 

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.