It should meet all the modeling requirements of a date table. If you're developing a DirectQuery model and your data source doesn't include a date table, we strongly recommend you add a date table to the data source. This way, your model leverages a single source of truth for time in your organization. It's typically the case when you're connecting to a data warehouse, as it will have a date dimension table. When your data source already has a date table, we recommend you use it as the source of your model date table. For more information, see Auto date/time guidance in Power BI Desktop. This approach, however, doesn't support a single date table design that can propagate filters to multiple tables. Using this option can also be convenient when creating ad hoc models or performing data exploration or profiling. ![]() We recommended that you keep the Auto date/time option enabled only when you work with calendar time periods, and when you have simplistic model requirements in relation to time. Reports authors can work with time intelligence when filtering, grouping, and drilling down through calendar time periods. ![]() The Auto date/time option delivers convenient, fast, and easy-to-use time intelligence. So, whenever someone develops a new model, they can begin with a consistently defined date table. Share the template with all modelers in your organization. So, whatever technique you decide to use, we recommend you create a Power BI Desktop template that includes a fully configured date table. What's more, within an organization a date table should be consistently defined. ![]() A date table is perhaps the most consistent feature you'll add to any of your models.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |