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 guys,
In one of my PBIX, I have one Star Scheme that have only one DATE column, in this case, I´m using the parameter in PowerBI Desktop which creates one "virtual" date table for each Date column, this PowerBI @GuyInACube video explains: https://www.youtube.com/watch?v=2f7dYB1l84g
In another PBIX, I have an Star Scheme but the main table have MULTIPLES date columns, in this case, should I create one DATE TABLE manually or can I continue using the parameter? Which one is better for performance?
Plus, there´s any explanation why Date and time should be saparated?
@GuyInACube let´s check if you are online 😜
Best Regards,
Bruno
Hello @HarishKM , thank you for your reply.
I have read this article but what I don´t understand is this:
"However, having a calendar table gives two big advantages:
- It allows you to aggregate data by non-standard columns (think your company’s financial year, or your timesheet weeks, or the Mayan calendar!).
- It gives you access to all of the wonderful time-intelligence functions in DAX, with names like TOTALYTD and CLOSINGBALANCE. Without a calendar table these won’t work."
This is not actually true, since the video that I´ve shared explains that PowerBI do this by itself with the parameter of time intelligence marked as true.
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 |
---|---|
60 | |
58 | |
54 | |
36 | |
33 |
User | Count |
---|---|
79 | |
66 | |
45 | |
45 | |
43 |