There’s a requirement to sequentially traverse a collection in PowerApps. The issue is that, unlike a normal array in any programming language, we cannot directly access a collection’s item via indexing, in PowerApps i.e., we can’t dynamically read values at any index of a collection.
We had this requirement where we needed to create ~100 (parent/child) QuickLaunch links pointing to a single modern SharePoint list. These links will be filtered view on the same list based on the selection. We knew, that in modern SharePoint, instead of creating 100 different views, we can simply filter a list using specified query string parameters. The issue in hand were, how to:
Generate the URLs on Managed Metadata (Termstore) field for QuickLaunch
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.