Forum Discussion
Dynamics Nav 2015 Odata authentication problem
Hi,
I have a Odata connection that works perfect with Excel. Here´s the connection string:
Data Source=http://nav.impeto.local:9048/IMP-PRD-2015/OData/Company('SERVICOS')/Dimensoes;
Namespaces to Include=*;
Max Received Message Size=4398046511104;
Integrated Security=Basic;
User ID=XYZ;
Persist Security Info=false;
Base Url="http://nav.impeto.local:9048/IMP-PRD-2015/OData/Company('SERVICOS')/Dimensoes;
Password=PWY
Unfortunally, I can´t access it through Power BI desktop: it understands that it´s a oData URL, but it returns a "The user was not authorized" error, no mather what kind of authentication I use (basic / windows)
Any ideas?
9 Replies
Hi,
Are you using the latest powerbi desktop? If not, please update and try it again.
If the issue is still there, please follow the steps in articles below to see if it can be solved. And there is a similar case here.
Best Regards
Alex
Hi Alex,
I am using the latest version of powerbi desktop.
The similar case was solved by support?!? There´s no clear solution about it.
unfortunally these articles, doesn´t apply to my problem:
1) The data is never showed, unless I import the excel file from PB.
2) It´s not a cashe problem
We're having the issue with Nav 2016, cannot connect with Power BI unless the service tier is set to navuserpassword. Windows authentication does not work but from excel/using a web browser to access the port it works great.
Hi there,
Still no answer to this problem?! A colleague got the same message yesterday and we cant figure out why. The workaround doesnt seem like a satisfying option, we want to know what causes the problem and why some get it and some dont..
Hope you can help! :)
Hi rrosendahl,
No answer. We´ve opened a bug at Microsoft and after 3 months they didn´t give us any solution at all.
Hi Marceloerthal,
Thx for the reply. Like I said in my previous post, I would like to understand where it comes from. It would make it a whole lot easier to search within the differend programs to see of all the settings are right. Is it a Power BI issue? Or a NAV2016 issue? Or even something else that I dont know about (like software between both programs to help them communicate?). Or just a bug...
I'm still trying to figure it out with some colleagues. If we know where it comes from I'll let you know. Till that time (if it even comes ;)) I hope we can get some more info from this forum.
I had a similar issue to the one reported here.
In my case when calling the OData feed URL, I used the IP Address of the NAV server instead of the machine name. This worked straight away.
This root cause was not not the lack of a DNS server on our enviroment as I did manage to get the JSON file when I pasted the OData URL (with the machine name) into the browser. For some odd reason which I still can't figure out, PowerBI was returning "The User was not authorised" error in PowerBI when referring the machine name.
Hope this helps.
Hi EA25,
Thx for the comment. Go to know that there is a way to work around this problem. The next time I will encounter this problem I'll try to use the IP instead, to see if it works for me too.
Now we only have to figure out why it happends! ;)
Indeed.
It would be helpful if someone from MS can shed some light about this.
