Currently Web.Headers only returns generic response headers. Most APIs return paging information(count, start,end) in response headers. Exposing custom response headers would significantly speed up integration of APIs to feed data in Power BI
4 Comments
- jpr2New Member
+1 on this. The Shopify REST api, for example, sends back pagination information in the header. Since it is filtered out but needed, you have to develop a custom connector, which then requires a Gateway.
If the response headers were available, this could all be done without need of a connector.
- joseph_singh_frFrequent Visitor
+1 for me too. I need to connect to my CMDB ( Spider) API, the authentication token is return within the response header. Since only a subset of the header is return, I have to create a custom connector to authenticate to the API and download the information into PowerBI.
- fbcideas_migusrNew MemberStatus added:New
- grantmdRegular VisitorLet me paginate PLEASE
Recent ideas
Allow Managed Private Endpoint to be disabled/enabled per notebook
Could notebooks have an option to use or not use the workspace's Managed Private Endpoint (MPE)? MPE can significantly increase notebook startup time, even for notebooks that don't need private conn...frithjof_v13 hours agoCommunity ChampionNew21Views1like0CommentsMatrix: column totals as a bar chart docked to the edge
What's missing Data bars already work on the Total row and column through conditional formatting, so row totals can be read as length. Column totals cannot: they render as a horizontal bar inside a ...Sayurivalente1 day agoRegular VisitorNew80Views6likes1Comment