131 posts tagged with "Low Code"

The solution checker reads everything in a solution against Microsoft's best-practice rules and lists what it finds, each with a severity and a link to guidance. This guide runs it in Power Apps, reads the results, and runs the same check from the Power Platform CLI, whose result file also says which control each issue is on.

The app needs two SharePoint lists with exact column names, and so far they exist only because Part 2 made them by hand. This part builds a Power Automate flow that creates both lists, their settings and all 16 columns on any site, and that can run again without changing anything.

Before a flow removes something, it should check that it's there. contains() answers that: does this array include this value? This guide uses it to check whether a SharePoint view shows a column before a step removes the column from it.

Sometimes you don't need a whole Condition with two branches, just one value or another. if() does that inside an expression: give it something true or false, and the two values to choose between. This guide uses it to write a Boolean into a JSON body correctly.

A Condition splits a flow in two: the steps in its True branch run when a comparison is true, and the ones in False when it isn't. This guide adds one in the new designer, compares an expression with true, and adds a step to the branch that needs it.

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.