This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi,
What is the best approach to combining data from two tables (Actuals and Forecast in the example below), so both the Actual and Forecast field are available in the resulting table when some rows match and some don't.
Merging using a full outer join results in the following:
Would you then just create a new name field something like this:
Taking the value from Name if it's not null or from Forecasts.Name if Name is null.
Resulting in this:
Which can obviosuly then be tidied up:
Is there a better way of achieving the same thing?
Hi @seamie82 ,
The way I would approach this is to unpivot both the Actual and Forecast columns, append the two tables together and then rename 'Attribute' to Type.
That would give you this table:
Then in your measures you can use
CALCULATE ( [measure] , Table[Type] = "Actual" )
or
CALCULATE ( [measure] , Table[Type] = "Forecast" )
to use the two different sets of values.
@seamie82 , Power query append.
Append : https://radacad.com/append-vs-merge-in-power-bi-and-power-query
Or common tables https://amitchandak.medium.com/power-bi-when-i-asked-you-to-create-common-tables-a-quick-dax-solutio...
Thanks, I read this already: https://radacad.com/append-vs-merge-in-power-bi-and-power-query
If you used append though would you do something like this?
Adding a descriptive column to each source and then appending:
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 39 | |
| 28 | |
| 28 | |
| 22 | |
| 18 |
| User | Count |
|---|---|
| 67 | |
| 37 | |
| 32 | |
| 27 | |
| 25 |