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
Fix links generated in multi tenant setups
When I log into Fabric, and I have access to multiple tenants, the links generated for things like monitoring URLs in pipeline runs do not include "ctid=<tenantguid>" query string value, which appear...jwisemanfs2 hours agoNew MemberNew3Views0likes0CommentsDedicated Fabric Message Center to communicate planned Fabric Changes
Summary Microsoft recently rolled out a change that automatically enabled the Item Recovery tenant setting in Microsoft Fabric for tenants where the setting had not been explicitly configured. Accor...Edgar_11 hours agoNew MemberNew33Views5likes0Comments