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

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Grumelo
Advocate II
Advocate II

Don't use Odata!

Don't use OData Connector!

Don't retrieve your data with OData.Feed()!

 

WHY ?

 

Because until it's fixed the OData connector is not at all doing what you are expecting.
Data retrieval is slow like hell and even worst the size of retrieved data is too huge.

This is because many many HTTP requests are executed instead of a single one.

 

Even if your use the ODataVersion Parameter or request JSON format; OData.Feed() is just a no go.

OData.Feed("URL",[],[Odataversion=4]) is maybe improving the problem but not solving it.

 

WHAT ELSE ?

 

The best alternative when trying to retrieve OData feed is the following

 

Json.Document(Web.Contents("your REST call",[Headers=[accept="application/json"]])

 

Example when retrieving data from a SharePoint space

 

Json.Document(Web.Contents("https://XXXX/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget,ModifiedBy/Name&$expand=ModifiedBy",[Headers=[accept="application/json"]]))

5 REPLIES 5
Grumelo
Advocate II
Advocate II

This is what Power BI desktop is doing when using OData.Feed()

 

ResultProtocolURLBodyCachingContent-TypeProcess
200HTTPS/BI_Demo/_vti_bin/listdata.svc/$metadata113,170no-cacheapplication/xml;charset=utf-8microsoft.mashup.container.netfx40:9188
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=Budget,Id,WineType,Year23,969no-cacheapplication/atom+xml;charset=utf-8microsoft.mashup.container.netfx40:6636
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget813no-cacheapplication/json;charset=utf-8microsoft.mashup.container.netfx40:9188
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget813no-cacheapplication/json;charset=utf-8microsoft.mashup.container.netfx40:9188
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget22,700no-cacheapplication/atom+xml;charset=utf-8microsoft.mashup.container.netfx40:9188
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget813no-cacheapplication/json;charset=utf-8microsoft.mashup.container.netfx40:6636
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget813no-cacheapplication/json;charset=utf-8microsoft.mashup.container.netfx40:6636
200HTTPS/BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget22,700no-cacheapplication/atom+xml;charset=utf-8microsoft.mashup.container.netfx40:6636
arify
Microsoft Employee
Microsoft Employee

Hi Grumelo,

 

Can you please send us a frown with the Fiddler traces?

 

Thanks

I've done it already several days ago, email was send to: pbidesfb@microsoft.com sender was Fred Lorrain from fred.lorrain@atos.net

arify
Microsoft Employee
Microsoft Employee

Thanks, we'll take a look at it and will let you know 🙂

By the way, this issue of calling many time the data source is not limited to OData.feed(); same kind of problem with XML.Document(); I've noticed at least two calls instead of one.

 

And in Query edit mode it's even worst.

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.