Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi,
I am noticing a lot of LocalDateTables showing up in Tabular Model Editor when I connect to my pbix file.
I also see a lot of LocalDateTables as TMDL files when I save my report as a pbip.
I don't understand. My model uses Direct Query to a Calendar Table.
I also have Auto date/time turned off.
So I have no idea where these tables are coming from.
Anyone know?
Thanks,
Solved! Go to Solution.
Hi @mp390988 ,
Thank you for reaching out to the Microsoft Fabric Community Forum and for confirming Auto date/time is off . Also thank you @Tahreem24 and @cengizhanarslan for your helpful response.
The behavior you’re seeing is expected. Even when Auto date/time is turned off, Power BI does not remove LocalDateTable_ objects that were created earlier in the model’s lifecycle*. These tables can still appear in Tabular Editor and PBIP/TMDL files, although they remain hidden and are not used by visuals or DirectQuery queries.
Disabling Auto date/time only prevents new local date tables from being generated. It does not retroactively clean up existing system-generated artifacts.
If you want to eliminate them entirely, the only supported approach is to recreate the model in a new PBIX with Auto date/time disabled from the start. Otherwise, they can be safely ignored and will not impact report results or performance.
Thank you.
Hi @mp390988 ,
We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.
Thank you.
Hi @mp390988 ,
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.
@mp390988 ,You must disable it in both places:
Global :
File → Options → Data Load → Auto date/time
Current file:
File → Options → Current File → Data Load → Auto date/time
I confirm the Auto date/time is off (did also mention that in my OP).
Hi @mp390988 ,
Thank you for reaching out to the Microsoft Fabric Community Forum and for confirming Auto date/time is off . Also thank you @Tahreem24 and @cengizhanarslan for your helpful response.
The behavior you’re seeing is expected. Even when Auto date/time is turned off, Power BI does not remove LocalDateTable_ objects that were created earlier in the model’s lifecycle*. These tables can still appear in Tabular Editor and PBIP/TMDL files, although they remain hidden and are not used by visuals or DirectQuery queries.
Disabling Auto date/time only prevents new local date tables from being generated. It does not retroactively clean up existing system-generated artifacts.
If you want to eliminate them entirely, the only supported approach is to recreate the model in a new PBIX with Auto date/time disabled from the start. Otherwise, they can be safely ignored and will not impact report results or performance.
Thank you.
Those LocalDateTable_* objects are almost always created by Power BI for “auto date/time” style hierarchies behind the scenes.
In Desktop, confirm Auto date/time is off in Options → Data Load (both Current File and Global, if applicable), then save and republish.
Also keeping thos elocel date tables would increase your model size, thus decreases your rendering and process performance. Disabling this option is the best practice option always.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 39 | |
| 38 | |
| 38 | |
| 28 | |
| 27 |
| User | Count |
|---|---|
| 124 | |
| 89 | |
| 73 | |
| 66 | |
| 65 |