How to get an HOURLY Time Table data in Bravo #489
-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
In order to use Time Intelligence functions, you should keep a Date table with only one row per day. The best practice is to move the hour (or the time within a day) into another dimension, splitting the date and time into two columns in your fact tables. https://www.sqlbi.com/articles/optimizing-high-cardinality-columns-in-vertipaq/ Bravo implements the same patterns described here: https://www.daxpatterns.com/time-patterns/ I would not suggest you add a column to your Date table, because it would break the time intelligence calculations. However, if you want to do that, the way to go is by creating a customized template as described in the documentation (work in progress, we'll also add videos later, we are working to complete that before v1): https://docs.sqlbi.com/bravo/features/manage-dates/customize-date-template In the future (after v1) we might consider adding additional templates for a separate Time table (just hours, hours/minutes, ...), but it's not planned for v1 for sure. Thanks! |
Beta Was this translation helpful? Give feedback.
In order to use Time Intelligence functions, you should keep a Date table with only one row per day. The best practice is to move the hour (or the time within a day) into another dimension, splitting the date and time into two columns in your fact tables.
https://www.sqlbi.com/articles/optimizing-high-cardinality-columns-in-vertipaq/
https://www.sqlbi.com/blog/alberto/2019/03/25/using-dax-with-datetime-values/
https://www.sqlbi.com/articles/automatic-time-intelligence-in-power-bi/
Bravo implements the same patterns described here: https://www.daxpatterns.com/time-patterns/
I would not suggest you add a column to your Date table, because it would break the time intelligence calculations. H…