Showing results for 
Search instead for 
Did you mean: 

Native SharePoint HTTP (Rest) Action for PowerApps

Right now, the SharePoint connection works great for simple use cases, but there are many more complicated use cases arent really working great with out of the box.  


A really useful feature/maybe connector would be a SharePoint HTTP action (similar to Flow) that can use the credentials of the current user to make the HTTP Rest call to SharePoint in the context of the current user.  This would ensure:

  • You only get the items that the user has access to
  • You can get around list lookup limitations of SharePoint
  • You can get around the delegation and large list filtering


I'd imagine your source on a form or gallery might be something like this:


Items: SharePoint.HTTP("'guidhere...)", "applicaton/json;odata=nometadata")


Which would return a json of of an individual list item.


Items: SharePoint.HTTP("'guidhere...", "applicaton/json;odata=nometadata")


Which would return a json of of all the list items.  


Then users could tailor the content with the sharepoint odata in the URL, and you dont have to mess with connections that use admin crednetials or enterprise applicatons and keys.

Status: New
Level 8

Something to add here. I'm using Onedrive at the moment for the thumbnail option but, it would be possible to use the much more powerful Sharepoint REST API to retrieve small sized images for the original big image. 

To understand better:

Sadly, it's not working for some mysterious reasons but, this would be one big advantage of using the REST API.



You should check out my latest "AMAZING" demo app I have developed for a corrosponding blog I will most likely post within the next week. 


For this demo app I do still use the SharePoint HTTP action in 5 Flows I have implemented to enable all the almost unbelievable functionality you'll see in a demo video I have posted on YouTube yesterday. Believe me it's worth watching Smiley Wink.


Whilst the request for this idea is to provide some kind of equivalent Connector you can create for your apps whereby App Makers could then tailor the content with the sharepoint odata in the URL, there is absolutely no reason you cannot effectively accomplish the same thing by passing that odata query string as a parameter to a Flow.


Perhaps the most significant obstacle to overcome is that PowerApps requires a well defined schema definition in the Response action that return the data from SharePoint to PowerApps. The same however is required for any Connector for that matter. I figured out a workaround to this though for this latest demo app I've created which I'll explain in more detail in my latest blog.


Without associated a single Connector to the demo app, I've essentially create a complete SharePoint UI within my app that consists of one screen. That's all. In that one screen users can view all the content they have permission to access stored on any site in SharePoint, view all the Document Libraries, Lists and Subsites for the site they've connected to, view PDFs, Word and PowerPoint documents, and potentially other types of documents within their apps, view the metadata for column columns they may have created on Lists, view highly compressed photos stored in the Site Assets or other Document Libraries for that matter as well as videos they may have uploaded into Document Libraries. All of that on one screen in one app. 


The type of functionality showcased in the demo app I created address countless feature requests many App Makers have been frustrated for years about, and yet in the demo I have only touched the surface insofar as what IS possible to implement within PowersApps for quite some time in fact,


Coming soon Smiley Wink