Microsoft Power Platform Low-Code Services
View All Tags
A search that finds nothing returns an empty array, and the flow often needs to know that: create the list only if it isn't there yet. empty() answers with true or false. This guide uses it in a Condition.
When an action returns data, such as a SharePoint REST request's response, later steps read it with body(). Name the action, then pick the property you need. This guide reads a single value and an array from real responses.
Inside an Apply to each loop, items() gives you the item the loop is working on right now. Add ?['name'] and you get one of its properties. It's the expression you'll write most inside loops, and nested loops are where its loop name matters.
Dynamic content gives you values from earlier steps as they are. When you need to work with a value, such as reading one property of a loop's current item, you write an expression. This guide adds one to an action's field in the new designer, and checks what the flow saved.
When a flow needs several actions that are almost the same, build one, then copy it. The copy keeps every setting: the site, the method, the headers and the expressions. You only change what's different. This guide copies an action in the new designer, pastes it where it's needed, and uses the same moves to move an action into a condition.
Apply to each runs the steps inside it once for every item in an array: every list to create, every column to add, every row a search returned. This guide loops over a JSON array, reads the current item inside the loop, and nests a second loop over each item's own array.
The SharePoint connector has ready-made actions for items and files, but not for everything, such as creating a list with its columns. Send an HTTP request to SharePoint fills the gap: it calls SharePoint's REST API with your connection. It's part of the standard SharePoint connector, so it needs no premium license. This guide builds a first request that reads a site's title.
Compose holds a value for the rest of the flow: a number, some text, or a whole JSON document. Later actions use it as Outputs. It's the simplest way to keep a flow's settings in one place, and this guide uses it for exactly that.
You don't need to leave the designer to try a flow. Test runs it there, asks for any inputs, and shows each step's result on the canvas with how long it took. This guide tests an instant flow and reads what came back.
An instant flow can ask for a value every time someone starts it: a site address, a date, a name. You add the question to the Manually trigger a flow trigger as an input, and the rest of the flow uses the answer. This guide adds a text input and gives it a name and a description people understand.
