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

Fabric Data Days Monthly is back. Join us on March 26th for two expert-led sessions on 1) Getting Started with Fabric IQ and 2) Mapping & Spacial Analytics in Fabric. Register now

Odata

Power query natively selects all data from the odata feed, and allow you to filter or select columns after having retrieved the data. This takes for ages to pull data to power BI. I suggest a feature change to allow the field and filter selection to be applied in the odata feed using the "somethingSet?$select=Field1,Field2..... It dramatically reduces the load time, and its less hard on the infrastructure at Microsoft 🙂
Status: Completed
Comments
fbcideas_migusr
New Member
The power query pulled a bit over 4 Gb on a table with 220K records of data through the Odata feed, and after applying the select criteria the query is only pulling 350 Mb datam and the query is at least 4 times faster.
fbcideas_migusr
New Member
Hi miquel i agree that it is possible to build a custom rule string with filters and field selection. However the approach isn't really user friendly and the ordinary user will not be able to do this. I suggest to use The Navigator to selection fields and filter date, but build The Full URL, and thereby filter data on server site instead Of Client site
barta
New Member
It should indeed be more user friendly to enter oData parameters
guido_leenders
New Member
Our users specify the transformation in the preview of Microsoft Power BI Desktop. In that case it works fine, even with millions of financial transactions.
fbcideas_migusr
New Member
Status changed to: Completed