Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
I’m working on a Power BI dashboard that pulls data from five different sources, each with its own schema and no relationships between them.
Each source contains its own date field and unique measures. I want to create a single table visual that:
Uses a common date column (Month/Year) in the table
Displays two measures side-by-side:
Total Sales Closed (from one source)
Total Tasks Closed (from another source)
The goal is to synchronize these measures by date, even though the datasets are unrelated.
What I’ve Tried:
Created a disconnected Date table using CALENDAR() and added columns like Year, Month, and YearMonth.
Used TREATAS in DAX to align each measure with the disconnected Date table.
Created a new column to strip time from the datetime fields using INT() and DATEVALUE().
Built measures using CALCULATE + FILTER + TREATAS.
Despite this, the measures return blank values in the visual.
Request:
I need guidance on:
How to correctly sync measures from unrelated datasets using a disconnected Date table.
Why the current approach using TREATAS and cleaned date columns might be failing.
Best practices for building a unified visual when sources are not related.
Solved! Go to Solution.
The approach you are using should work, but you need to make sure that the date columns you are using in all the models are just dates, not datetimes. The disconnected table you are using will be fine, as you are generating that using CALENDAR and so it will not have a datetime part, but in the other models you need to make sure that the column is set to date both in Power BI Desktop and in Power Query - if you only do it in desktop but not in Power Query it will retain the time information even though it won't show it.
Once you are happy that all columns are purely dates you could use TREATAS as you have suggested, or you could create one-to-many relationships from the date table in the combined model to both date tables in the other models, so that filters flow from the combined model to the other models. That would negate the need to amend any calculations and you would be able to use the base measures from both models.
Hi @AppleBoy ,
@sivarajan21, response matches your requirements well. Please review it and let us know if you need any more information.
Thanks for quick response @sivarajan21 & @johnt75 .
Thank you.
Hi @AppleBoy
I have tried this using a sample dataset and it works.
Semantic model:
The dax measures used are:
Total Sales =
CALCULATE (
SUM ( 'Sales (Source 1)'[Amount] ),
TREATAS ( VALUES ( 'Date'[Date] ), 'Sales (Source 1)'[CleanDate] )
)Total Tasks Closed =
CALCULATE (
COUNTROWS ( 'Tasks (Source 2)'),
TREATAS ( VALUES ( 'Date'[Date] ), 'Tasks (Source 2)'[CleanDate] )
)Output:
Please let me know if this is what you want?
Best regards,
The approach you are using should work, but you need to make sure that the date columns you are using in all the models are just dates, not datetimes. The disconnected table you are using will be fine, as you are generating that using CALENDAR and so it will not have a datetime part, but in the other models you need to make sure that the column is set to date both in Power BI Desktop and in Power Query - if you only do it in desktop but not in Power Query it will retain the time information even though it won't show it.
Once you are happy that all columns are purely dates you could use TREATAS as you have suggested, or you could create one-to-many relationships from the date table in the combined model to both date tables in the other models, so that filters flow from the combined model to the other models. That would negate the need to amend any calculations and you would be able to use the base measures from both models.
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 60 | |
| 49 | |
| 30 | |
| 25 | |
| 23 |
| User | Count |
|---|---|
| 130 | |
| 103 | |
| 58 | |
| 39 | |
| 31 |