Forum Discussion
Nullable object error message on almost all tables but ERP dev can access on their end?
Hello!
I'm having this same error message occur on most of my tables trying to access the data. I can view pretty much any "view" but when I try to access a "table" the below error message occurs (first pic). I was able to access these at one point however they stopped working and have not been able to use them since. We've coordinated with our ERP developers and they are able to access the data tables on their end using our same credentials. Specifically this what they said "I’ve configured the ODBC on my end and within Excel I am able to successfully access both Tables and Views with the xxxx User". I've attached the picture of him showing me this works. He has said that he believe it's a Power BI issue.
Does anyone have advice on how to resolve this? The "views" don't provide the same information necessarily as the tables do. And some tables I can access - but the majority do not. I don't want to extract to excel because that would defeat the purpose of having power bi connect to the data base. If I did it the excel way I'd have to manually update the excel sheet instead of it just refreshing with the latest data straight from our ERP.
Thank you in advance!
- Anonymous2 years ago
Hi KIBI2024
This issue has been confirmed as a known issue internally.
This issue is currently being fixed.
Please be patient to wait for fixing. If there is any news, I will update it here.
Best Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
5 Replies
- lbendlin
Super User
Did you click the "Report this issue" button?
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .- KIBI2024Regular Visitor
i reported the issue, thanks!
- AnonymousNot applicable
Hi KIBI2024
This issue has been confirmed as a known issue internally.
This issue is currently being fixed.
Please be patient to wait for fixing. If there is any news, I will update it here.
Best Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.