Power BI
Needs VotesOdata.Feed should have RelativePath as an option the same as Web.Contents.
Robert Charlton-Ward on 11 Mar 2021 15:55:51
This would be very useful to avoid "dynamic query" errors when refreshing on the web service.
As it is, calling an API that has a slightly different endpoint to request an authentication token than it does for the main request means the query gets treated as having two separate sources, which is a no-no on the web service.
Being able to specify a relative path to both endpoints from the base URL would mean it was treated as one source and no longer be considered a dynamic query.
- Comments (2)
RE: Odata.Feed should have RelativePath as an option the same as Web.Contents.
Same here. We provide OData API which brings great flexibility to our customers, but at the same time we need to encourage our customers to implement incremental refresh in their reports - but incremental refresh does not work with dynamic queries, and since OData does not support RelativePath, the customers will have to use Web.Contents instead.
RE: Odata.Feed should have RelativePath as an option the same as Web.Contents.
This is extremely important for us as well. We've built an OData feed provider for MYOB and Xero but we need to have the ability to have a main root path and a relativepath (similar to Web.Contents) in order to be able to provide the ability to automatically consolidate data.