Forum Discussion
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 ...
This is what Power BI desktop is doing when using OData.Feed()
| Result | Protocol | URL | Body | Caching | Content-Type | Process |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/$metadata | 113,170 | no-cache | application/xml;charset=utf-8 | microsoft.mashup.container.netfx40:9188 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=Budget,Id,WineType,Year | 23,969 | no-cache | application/atom+xml;charset=utf-8 | microsoft.mashup.container.netfx40:6636 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget | 813 | no-cache | application/json;charset=utf-8 | microsoft.mashup.container.netfx40:9188 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget | 813 | no-cache | application/json;charset=utf-8 | microsoft.mashup.container.netfx40:9188 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget | 22,700 | no-cache | application/atom+xml;charset=utf-8 | microsoft.mashup.container.netfx40:9188 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget | 813 | no-cache | application/json;charset=utf-8 | microsoft.mashup.container.netfx40:6636 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget | 813 | no-cache | application/json;charset=utf-8 | microsoft.mashup.container.netfx40:6636 |
| 200 | HTTPS | /BI_Demo/_vti_bin/listdata.svc/GreenWinerySalesBudget?$select=WineType,Year,Budget | 22,700 | no-cache | application/atom+xml;charset=utf-8 | microsoft.mashup.container.netfx40:6636 |
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: [email protected] sender was Fred Lorrain from [email protected]
Thanks, we'll take a look at it and will let you know :)
