In this post, I’ll demonstrate how to run any SharePoint REST API directly from MS Flow. MS FLow already provides lots of action cards OOTB. For ex, create a list, delete a list, etc. However, it doesn’t contain action cards for, let’s say, every possible operation within SharePoint. Microsoft has intentionally provided, only the commonly used actions to MS Flow. This also makes sense because, one of the key attribute of MS Flow lies in its simplicity and how, even a business user can perform simple tasks on their own. Rather than having the users lost in a plethora of choices, they are presenting them with only a list of commonly used tasks. For everything else, there’s REST API.
This post is about directly applying aggregations on a SharePoint List, without specifying any grouping condition. If you want to group SharePoint List data before applying aggregation then, refer to this post, SharePoint Group By.
I must admit that this turned out to be little tricky than what I had imagined. The situation was fairly simple. I had a SharePoint List. I had applied couple of Totals functions, Standard Deviation & Variance, on one of its Number field in two separate custom views. I just wanted to retrieve those values from client side. That’s it! My initial assessment was there must be some function/property that I can easily query from the client. As it seemed initially, there’s no direct way of doing that. Fine, just another day at the office for a SharePoint developer 😉
When a SharePoint List/Library is marked hidden, SharePoint simply removes there navigation point from the SiteContents. The actual List/Library still continue to exist at their respective urls, the format of which remains in sync with any other SharePoint List/Library.
So to access a hidden SharePoint List, navigate to: