Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi everyone!
I'm connecting from Excel to Power BI semantic models that have Incremental Refresh enabled. However, when I choose the "Insert PivotTable" option, it loads the tables from the semantic model (such as "Metrics" in the attached image), but it also includes several tables named LocalDateTable_*.
These LocalDateTable tables are auto-generated and there are more than 10 of them, which clutters the field list. I would like to prevent these tables from appearing when inserting a PivotTable from a semantic model connection in Excel.
Is there a way to hide or exclude them?
Thanks
Solved! Go to Solution.
Hi @julsr ,
Yes, if you have multiple semantic models, you'll need to disable Auto Date Time individually for each one, as the setting only applies to the specific model. Turning it off in one model does not impact the others. Disabling this feature will not affect Incremental Refresh or disrupt your model. Incremental Refresh relies on the date column defined in the refresh policy on the fact table and does not depend on the automatically created LocalDateTable tables.
By turning off Auto Date Time, you take direct control over your date logic. Instead of Power BI generating hidden date tables, you create and manage a visible calendar table, which is then used for filtering, reporting, and time intelligence in both Power BI and Excel. This calendar table does not need to be included in the Incremental Refresh policy, and it does not change data partitioning or refresh behavior.
There is no loss in functionality your visuals and PivotTables will continue to work as before, and often with greater predictability due to the use of a single shared Date table. Additionally, the absence of LocalDateTable entries in Excel keeps the field list more organized. This approach is recommended for production semantic models, particularly when sharing and using Incremental Refresh.
Best Regards,
Tejaswi.
Community Support
Hi @julsr ,
Thanks for reaching out to the Microsoft fabric community forum.
The behavior you’re experiencing when connecting Excel to a Power BI semantic model is expected. The LocalDateTable_* objects you see are not manually created tables; they are automatically generated hidden date tables produced by the Power BI engine when the model includes date columns and the Auto Date/Time feature is enabled. Excel displays these internal tables in the field list, making them more visible than in Power BI Desktop.
Currently, Excel does not provide a supported method to selectively hide or exclude only the LocalDateTable_* tables after they have been created.
To prevent these tables from appearing, it is best to disable Auto Date/Time in your semantic model and implement a dedicated Date dimension table. Create a calendar table, designate it as the official Date table, and establish relationships from your fact tables to this calendar table. This approach will prevent Power BI from generating multiple LocalDateTable_* objects, and they will no longer appear in Excel.
In summary, while it is not possible to hide these tables directly in Excel, you can avoid them entirely by turning off Auto Date/Time and using a proper Date table, which is also considered best practice for incremental refresh models.
Best Regards,
Tejaswi.
Community Support
Thank you all for your answers! So, if I have 3 different semantic models connected to my original data source with Incremental Refresh, what I would need to do is disable the Auto date/time feature for each semantic model and create a dedicated datetime table that references the attributes in my table used by the incremental refresh? I didn't understand if I disable it, how could I achieve same results?
Hi @julsr ,
Yes, if you have multiple semantic models, you'll need to disable Auto Date Time individually for each one, as the setting only applies to the specific model. Turning it off in one model does not impact the others. Disabling this feature will not affect Incremental Refresh or disrupt your model. Incremental Refresh relies on the date column defined in the refresh policy on the fact table and does not depend on the automatically created LocalDateTable tables.
By turning off Auto Date Time, you take direct control over your date logic. Instead of Power BI generating hidden date tables, you create and manage a visible calendar table, which is then used for filtering, reporting, and time intelligence in both Power BI and Excel. This calendar table does not need to be included in the Incremental Refresh policy, and it does not change data partitioning or refresh behavior.
There is no loss in functionality your visuals and PivotTables will continue to work as before, and often with greater predictability due to the use of a single shared Date table. Additionally, the absence of LocalDateTable entries in Excel keeps the field list more organized. This approach is recommended for production semantic models, particularly when sharing and using Incremental Refresh.
Best Regards,
Tejaswi.
Community Support
Hi @julsr ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
Yes, it did, thanks!
However, this wasn't enough for some models, so I had to edit the TMDL file of my semantic model in Power BI Desktop to remove the LocalDataTables and all references to them.
Those LocalDateTable tables are auto-generated Auto Date/Time tables that Power BI creates when a model contains date columns and Auto Date/Time is enabled. I would advise you to disable them as shown below:
File > Options and settings > Options
→ Data Load
→ Uncheck "Auto date/time"
Hi @julsr
The LocalDateTable_* tables are system-generated tables created by the Tabular engine for internal date and time handling (including scenarios like incremental refresh).
Since Excel connects directly to the semantic model (not to reports), it exposes all model objects, including system tables.
Unfortunately, there is currently no supported way to hide or exclude these system tables when connecting to a semantic model from Excel.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 51 | |
| 40 | |
| 37 | |
| 14 | |
| 14 |
| User | Count |
|---|---|
| 85 | |
| 69 | |
| 38 | |
| 29 | |
| 27 |