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
Fabric UX Idea: Clearly Identify the Source Workspace for Opened Fabric Artifacts
In many Fabric implementations, organizations have multiple projects and environments, for example: Sales Analytics – Development Sales Analytics – UAT Sales Analytics – Production Similarl...Murtaza_Ghafoor5 hours agoSuper UserNew5Views0likes0CommentsCopilot in Power BI should be canvas-aware and support screenshots / direct visual debugging.
Currently, Copilot in Power BI cannot: See the actual canvas / selected visual Accept screenshots or images to aid in troubleshooting Both of these make debugging visual-level issues painful and...dcohare5 hours agoHelper INew8Views1like0Comments