Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowGet inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.
Hello,
I am currently building a data model, where I have various date/time columns. In this regard I found that according to best practices I should have a calendar table. Since I don't need the times I simply converted the date/time columns in PowerQuery to date columns and the issue was resolved. However, since I also want to have an incremental refresh on the table I need a date/time column.
What are the best practices in such scenarios? Do you always need a date column and a date/time column or there are some workarounds?
Solved! Go to Solution.
Hi @IvanKostov ,
If you need a date column (calendar relationship) and you need a datetime column (incremental refresh) then you need a date column and a datetime column, no way around that I'm afraid.
In Power Query, keep your datetime column as-is, then create a new custom column using the following:
Date.From([datetimeColumn])
Using Date.From will prevent query folding from breaking if your source is foldable.
Pete
Proud to be a Datanaut!
Thanks Pete!
Hi @IvanKostov ,
If you need a date column (calendar relationship) and you need a datetime column (incremental refresh) then you need a date column and a datetime column, no way around that I'm afraid.
In Power Query, keep your datetime column as-is, then create a new custom column using the following:
Date.From([datetimeColumn])
Using Date.From will prevent query folding from breaking if your source is foldable.
Pete
Proud to be a Datanaut!
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
29 | |
26 | |
23 | |
13 | |
10 |
User | Count |
---|---|
24 | |
21 | |
17 | |
11 | |
9 |