Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
I am trying to connect to our NAV2017 from PowerBI.com via an on-premise Gateway, using OdataV4.
Using the OdataV4 url in PowerBI Desktop or in a web browser will return correct data, but not when I use a Data Gateway.
Any help will be deeply appreciated.
Solved! Go to Solution.
I raised a ticket at Microsoft and together with them I found the problem.
- It turns out that to create a connection through a on-premise gateway you should use the root url, and not the complete url (e.g. https://nav.domain.xx:7048/NAV2017/ODataV4/Company('NAVcompany')/table will work in most other cases (PowerBI Desktop, in a web browser, et), but not in a on-premise gateway. Instead, it should be https://nav.domain.xx:7048/NAV2017/ODataV4).
I raised a ticket at Microsoft and together with them I found the problem.
- It turns out that to create a connection through a on-premise gateway you should use the root url, and not the complete url (e.g. https://nav.domain.xx:7048/NAV2017/ODataV4/Company('NAVcompany')/table will work in most other cases (PowerBI Desktop, in a web browser, et), but not in a on-premise gateway. Instead, it should be https://nav.domain.xx:7048/NAV2017/ODataV4).
You can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues . If you have a Pro license you can consider raising a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Thanks, I'll do that.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
39 | |
37 | |
32 | |
25 | |
24 |
User | Count |
---|---|
37 | |
29 | |
23 | |
21 | |
17 |