Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello,
still new with Power Bi and slowly getting to the point starting to migrate our reporting in Qlikview to Power BI.
I have a question about date table best practice:
instead of creating a date table through power query and/or DAX when refreshing data
(which you read most of the time in PowerBI books and tutorials), why not set up a Date table in Excel?
It might be much easier to create in excel all those extra columns belonging to a fiscal year that does not start in januari because you can immeadiately validate if they correct.
You could prepare a futureproof date table in excel spanning allready much more years than needed now, then importing that table into power query and only adjust start and end date based on parameters created in power query.
Is this something that is done? And what might be good reasons to do this or not do this?
thanx a lot!
Chris
Solved! Go to Solution.
Spot on. Calendar data is immutable. There is no good reason to calculate this over and over again in Power Query or DAX. Put your Excel reference table on a SharePoint and never worry about this again.
Spot on. Calendar data is immutable. There is no good reason to calculate this over and over again in Power Query or DAX. Put your Excel reference table on a SharePoint and never worry about this again.
ok, thanx for the comment!!
Chris
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
72 | |
68 | |
53 | |
39 | |
33 |
User | Count |
---|---|
70 | |
63 | |
57 | |
49 | |
46 |