Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi All,
This might be a basic question for some more experienced people, but I couldn't find any info anywhere else that would solve my problem.
I have recently created a table in Dataverse, and I try to get data from that table into my report in Power BI. In the Navigator section I can select the new table, but then on the right side of the window a huge error message shows up that says "DataSource.Error: Microsoft SQL: "Invalid object name...". See the screenshot below.
If I want to get data from tables that I created several days ago, no problem, but if I want to get data from any tables that I created today, it just simply not works.
My question is that do I need to refresh anything in the background to get it work? Or if not, what could be the reason of the error message?
Thanks,
kukszi
Did anyone ever get a reason as to why this might happen? It happens often to me, and I'd really like to know a solid fix.
Hi,
I'm experiencing the same issue. I found a solution that worked for me, hopefully it can help you too.
I went to the affected table in dataverse and edited the 'Doing a mail merge' option to be unchecked and re-saved the table:
I then published the table, and when I checked, the connection to Power BI was working as expected. I tested re-enabling the 'Doing a mail merge' option and re-saving/publishing the table. The connection with Power BI continued to work. I'm no expert in dataverse, but maybe re-saving the table is triggering something behind the scenes.
Hope this helps.
Thanks,
Sam
That worked for me, too. I turned that option on, saved the change, and then turned the option off.
Hi Sam,
Thanks for your answer. Actually, I didn't have to follow your steps because it now works. I waited a couple of days, and now I can get the data from the impacted table into Power BI. I'm sure there was a process that ran in the background, but have no idea what was that.
Anyways, definitely not an ideal solution to wait a couple of days after creating the table, but at least it works. Thanks for your suggestion.
Cheers,
kukszi