Forum Discussion
OLE DB or ODBC error - Cannot find table LocalDateTable
Hi all, I have a report I built with quite a few semantic model links and have recently added in some data from a sharepoint list. Everything was working fine and then last week I started getting this error and I have no idea how to fix it.
I've looked in the list of tables available from the sharepoint list link and there are quite a few with the same format of code shown in this error but none of the codes match either mentioned in this error. I've googled for hours and have found reports about hidden date tables but I don't know which one it is and whenever I try to delete a dat source it just throws up the error again and won't let me delete them...I was going to try doing this to find out which one is the problem...can anyone help me please? #desperate!
Hi samc_26,
I suggest reaching out to Microsoft Support by raising a ticket. Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Thank you
Hi Anonymous no sorry I gave up on it and started from scratch on a new report, I have a deadline and couldn't afford to waste any more time not getting anywhere (I spent about a week on and off trying to fix it). I suspect that data from one of the semantic models my report was connected to was changed hence the error but I couldn't find any information to suggest which one. Thank you anyway
7 Replies
That looks like one of the auto datetime dimension tables.
"Auto date/time tables are permanently hidden, even from modelers. They don’t appear in the Fields pane or the Model view diagram, and its rows don’t appear in Table view. Also, the table and its column can’t be directly referenced by DAX expressions"
If you use Dax studio or tabular editor you can see them.
Try turning auto datetime off for the model
Thank you, Deku , for your response.
Hi samc_26,We sincerely appreciate your inquiry on the Microsoft Fabric Community Forum.
In addition to the response provided by Deku , please find below some additional points that may help resolve the issue:
-
Power BI automatically generates hidden date tables when the Auto date/time option is enabled. These tables may sometimes cause issues. To identify such hidden tables, you may use tools like DAX Studio or Tabular Editor. In DAX Studio, you can examine the metadata to determine whether any hidden date tables exist.
-
Instead of relying on auto-generated date tables, you can create a custom date table using Power Query or DAX code. A custom date table provides greater control over date fields and helps prevent complications arising from hidden tables.
If you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members encountering similar queries.
Thank you.
Hi v-pnaroju-msft I have a custom date table which is what I've used in this report and I've tried to turn off the auto date/time under Time Intelligence but it just throws out the error again and won't let me apply the changes. I don't have access to DAX Studio or Tabular editor in my company so I don't have those options unfortunately. The report was working fine so I don't understand how it can just break like this. I can't update any part of it now because of this error ☹️
Hi samc_26,
I suggest reaching out to Microsoft Support by raising a ticket. Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Thank you
-
Hi samc_26,
Just checking, have you had a chance to open a support ticket, as suggested. If so, we'd love to hear the current status or any updates from that.
If the issue was resolved through the support ticket, it would be great if you could share the solution here as well. It could really help other community members find answers more quickly.
Warm regards,
Prasanna KumarHi Anonymous no sorry I gave up on it and started from scratch on a new report, I have a deadline and couldn't afford to waste any more time not getting anywhere (I spent about a week on and off trying to fix it). I suspect that data from one of the semantic models my report was connected to was changed hence the error but I couldn't find any information to suggest which one. Thank you anyway
Hi samc_26,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thanks for the update, and totally understandable sometimes starting fresh is the best way forward, especially with a tight deadline. If you ever do revisit the original report and identify what caused the issue (like changes in the semantic model), please consider posting an update here. It could be really helpful for others who might run into a similar problem. Best of luck with your new report!
If this solution helped, please consider marking the response as accepted and giving it a thumbs-up so others can benefit as well.
Best regards,
Prasanna Kumar
