OData Data Refresh - including custom Power Query formulas inclusing OData.Feed

[peterbb]

Please support OData Data Refresh - including custom Power Query formulas inclusing OData.Feed

[fbcideas_migusr]

We have a very similar request: We are extensively using Power BI's OData feature to retrieve data from Microsoft Dynamics NAV. Since a typical report needs to retrieve data from multiple data source it is time-consuming to change each OData.Feed () call when we are moving a report to another customer. We tried to build up the OData.Feed () from another query called ODataBasePath in order to create a single reference point where we can change the OData-connection. It could look like this in all queries: Source = OData.Feed(ODataBasePath & “ServiceName”) In Excel and Power BI Desktop this is working fine. However the scheduled refresh on PowerBI.com seems to be unable to handle this dynamic OData.Feed. It is giving this error message that the scheduled refresh is currently not available for this data source. It would be of great help for our standard reports.

[trutz1]

Hope this gets solved soon as it is really a pain to rewrite all URLs when moving from TEST to PRODUCTION environments

[thomas_kreklin2]

I have problem similiar to Julian. I also do user PowerBI OData queries. A have a portfolio report for projects where I access PWA (project online) and Sharepoint-projectrooms (lists within each projectrom) to accumulate and generate a portefolio report. Works 100% on PowerBI Desktop, but refresh fails on powerbi.com. I need the OData query to be dynamic and build the OData query string based on parameters before accessing the datasource.

[matt_cooper]

With the constraints of the Project Online data model, the ability to have a dynamic query to retrieve data from project sites is critical. It works in other tools and should really be the standard functionality.

[john_dawson1]

Essential to be able to do this. In our case we use a parameter to accept a user login which is used in the query

[Smithbster]

Is there an interim workaround for crawling project sites to extract list items yet?

[robin_pauletto1]

So painful not being able to script dynamic URLs... I can't understand how it could be so complicated to fix this and why it is not already done.

[philip_ford-hut]

This is essential for efficient data refreshed using the OData.Feed connector. I can create a dynamic query URL to filter by a date that is generated in PowerQuery and it will refresh perfectly in Power BI Desktop. However when I publish to the Power BI Service I get the dreaded "Query contains unsupported function. Function name: OData.Feed" error. The workaround of using a static query URL and then filtering in Power Query is much less performant.

[Anthony_Widdows]

Please can we get this issue sorted as it is very hard to push reports out to many customers when the url has to be hardcoded in order to get around this problem

[peter_kairies]

We use OData.Feed to connect SAP HCM through an enterprise gateway. SAP will keep query results ready as they are scheduled jobs. Each result can be called with a "?$filter=RUNNUMER eq [nb]" attached to the uri. So, to load a number of runs, I need to build a unique connection for every run. In PBI desktop, loading of a large number of runs can be done via ie. a table with a running number used as run nmb in the uri attachment, or with a recursive function, too. Right now, we use a workaround and save the result in an excel file on sharepoint. A computer will refresh the file once a day and save it to sharepoint. But, for data protection issues, we need the direct connection without having to save a copy in order to hand it over to power bi service.