Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
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.
User | Count |
---|---|
136 | |
73 | |
73 | |
58 | |
54 |
User | Count |
---|---|
194 | |
95 | |
63 | |
63 | |
51 |