Auto Date Tables Identified
Detects models using Power BI's automatic date/time feature, which generates hidden date tables that can bloat the model.
What It Detects
This flag identifies columns in the data model where Power BI has automatically generated hidden date tables. If the date range of a column spans many years, the auto date table generates unnecessary rows. Consider disabling "Auto date/time" in Power BI Options > Data Load, or narrowing the source date range.
Why It Matters
- Model bloat — Each date/datetime column gets its own hidden calendar table. A model with 10 date columns will have 10 hidden date tables, each with a full year-level hierarchy.
- Increased memory usage — Auto date tables span the full range of values in the column, often generating rows for years that are irrelevant to the analysis.
- Slower refresh times — More tables in the model means more processing during data refresh.
- Redundant with custom date tables — If the model already has a dedicated date/calendar dimension table, the auto-generated tables are completely redundant.
Trigger Conditions
A column is flagged when:
- The column has a Date or DateTime data type.
- Power BI's Auto date/time feature is enabled (globally or per-column).
- A hidden
LocalDateTable_*is detected in the model metadata for that column.
Note: This flag detects the presence of auto date tables, not a threshold count.
Output
| Field | Description |
|---|---|
reportName | Report name |
tableName | Table containing the date column |
columnName | Date column that triggered the auto date table |
dateRange | The min–max date range spanned by the auto table |
workspaceName | Workspace name |
Notes and Edge Cases
- Global setting — The "Auto date/time" feature is a global Power BI Desktop setting (File → Options → Data Load). Disabling it affects all new columns but does not retroactively remove existing auto tables from saved .pbix files.
- Custom date tables — If the model already includes a proper date dimension table, disabling auto date/time is strongly recommended to avoid duplication.
- Wide date ranges — Columns with erroneous dates (e.g.,
1900-01-01default values) can cause auto date tables to span over 100 years, significantly inflating model size.
Related Flags
- Automatic Hidden Tables — Detects the auto date/time feature at the model level.
- Unused Tables — Auto date tables that are never referenced in visuals may also appear here.