131 posts tagged with "Low Code"

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.

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.

A flow that has to move to another environment with its app belongs inside a solution. This guide creates an instant cloud flow, one that someone starts by hand, inside a solution, and then opens it in the new designer, which takes one extra step.

The app is built. This part tests it the way the brief describes it, as each person in the demo sales team: a manager who's also an employee, a response that's declined and sent again, a promotion, someone who leaves and someone who joins. There are no new screens, only real accounts, real data and three findings.

This part lets managers keep each job title's plan up to date: add a competency, change its level or remove it, from one Competency screen. Every change applies to everyone with that job title, so the screen says so, checks for duplicates, asks before removing, and tells reviewers when a plan changed under a response.

Adding an item and editing one need almost the same screen. Instead of building two, build one and open it in two ways: with the item's ID to edit it, or with a blank ID to add a new one. Each formula that differs asks one question, IsBlank(locCompetencyId).

Some actions deserve a second thought, such as removing something many people use. Instead of acting at once, the button asks a question on the same screen, with Yes and Cancel below it. Nothing happens until Yes, and screen readers announce the question.

A screen reader reads where the user is. When an action makes a message appear somewhere else, its users don't hear about it. A live region fixes that: screen readers announce whenever its text changes. In Power Apps, a classic Label becomes a live region with its Live property.