Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
burgesst
Frequent Visitor

Power BI desktop gives error (415) Unsupported Media Type with only certain OData feeds from NAV

Trying to connect Power BI Desktop to Microsoft Dynamics NAV 2016 via OData, both on premises.

 

Set up some OData feeds a few days ago, and those are still working. However, any new ones give the error "OData: Request failed: The remote server returned an error: (415) Unsupported Media Type. (Unsupported media type requested.)"

 

On one client, this can be fixed by replacing servername.domain.local with just servername in the Odata path, but on another it fails both ways.

 

You'd think it was a name resolution issue, but the exisiting Odata feeds to the same server address still work!

 

And ALL the Odata feeds work perfectly in Excel.  So why should only new ones be failing, and only failing in Power BI ?

 

Thanks

1 ACCEPTED SOLUTION
JvdW
Advocate I
Advocate I

I've been struggling with this same issue for a few hours, and I think i've found the solution. Power BI caches data from OData feeds, meaning it will hold the data from the first time you consumed the OData feed. When you want to add data from a new NAV object and enter the URL using "Get Data" Power BI will return a error, because according to the cached data the newly added object doesn't exist. I've found 2 ways to solve this:

 

1. Lets say NAV gives you the following OData URL: http://localhost:7048/DynamicsNAV90/OData/Company(CRONUS)/Query. In Power BI Desktop: when pasting this link in the OData-feed using "Get Data" remove the last part of the URL (http://localhost:7048/DynamicsNAV90/OData/Company(CRONUS)/). This will open the query editor and shows you all the available objects in NAV(according to the currently cached data). Now go to "Start" in the ribbon and click "refresh preview". The OData feed should now be updated and the correct objects should be shown. From here you can select the object you want to use and load it in.

 

2. In Power BI Desktop: Go to "File"  and select "Options". Under "Data Load" you have the option to clear the cache. After doing this you can use "Get Data" and "OData-feed" as normal and the URL won't return the 415 error. 

 

Quite simple but it worked for me!

View solution in original post

6 REPLIES 6
JvdW
Advocate I
Advocate I

I've been struggling with this same issue for a few hours, and I think i've found the solution. Power BI caches data from OData feeds, meaning it will hold the data from the first time you consumed the OData feed. When you want to add data from a new NAV object and enter the URL using "Get Data" Power BI will return a error, because according to the cached data the newly added object doesn't exist. I've found 2 ways to solve this:

 

1. Lets say NAV gives you the following OData URL: http://localhost:7048/DynamicsNAV90/OData/Company(CRONUS)/Query. In Power BI Desktop: when pasting this link in the OData-feed using "Get Data" remove the last part of the URL (http://localhost:7048/DynamicsNAV90/OData/Company(CRONUS)/). This will open the query editor and shows you all the available objects in NAV(according to the currently cached data). Now go to "Start" in the ribbon and click "refresh preview". The OData feed should now be updated and the correct objects should be shown. From here you can select the object you want to use and load it in.

 

2. In Power BI Desktop: Go to "File"  and select "Options". Under "Data Load" you have the option to clear the cache. After doing this you can use "Get Data" and "OData-feed" as normal and the URL won't return the 415 error. 

 

Quite simple but it worked for me!

The second method works perfectly. Thank you very much!

I used the second method (clearing the cache) and it worked perfectly.

Thank you for exact recommendation!

ptitta
New Member

Same problem here. Someone have a solution. Some Odata works fine other no why?

Trying to understand the reason could help the solution

 

GeertSchhneider
New Member

I have exctly the same issue  (not working in powerBI - working fine in excel) - did you found a solution ?

 

Helpful resources

Announcements
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.

Top Solution Authors
Top Kudoed Authors