Low-Code and No-Code Development Platforms
View All Tags
SharePoint gives every list item a number when it's created: its ID. To open one item on another screen, pass its ID with Navigate, and read the item there with LookUp(List, ID = ...). SharePoint can run that query itself, as long as you compare the ID with =.
Until now, only the person building the app has used it. This part publishes it, shares it with the team, and opens it as a team member who has nothing but a Microsoft 365 license. Then it builds the manager's side: a My team screen with each direct report, and a screen per person showing what's waiting for review and where their plan stands.
Power Fx has no Exists function, but you don't need one: LookUp returns the first record that matches, or blank when nothing does. Wrap it in !IsBlank(...) and you get true when a record exists. On SharePoint, it's delegable.
Live monitor records what a canvas app does while it runs: which button was selected, which data it fetched, how long that took, and warnings such as delegation. When a formula gives an unexpected result, it shows what really happened.
The first time someone opens a canvas app shared with them, Power Apps asks: Allow [the app] to access your data? The app uses their own SharePoint and Microsoft 365 connections, so each person agrees once. This guide shows the dialog and what it means.
A canvas app's web link opens it straight in a browser. You need it to tell people about an app you've shared, because sharing doesn't always notify them. There are two places to get it.
Sharing a canvas app with a security group lets every member run it, and anyone added to the group later gets the app without another share. This guide shares an app in the new Share dialog and covers two things it doesn't do: give access to your data, and tell people.
Saving a canvas app keeps your changes; publishing gives them to the people you've shared the app with. Until you publish, they keep using the previous version, or can't open the app at all if it was never published.
A plan only matters once people act on it. This part builds the screen where they do: each competency on My plan opens a screen where the person writes how they show it and sends it to their manager. The same screen shows what happened next: waiting for review, a comment to act on when it's declined, and a locked response once it's approved.
Every input control has a DisplayMode: Edit to change it, View to only show it, or Disabled. Set it with a formula and the same box can be editable for a draft and read-only once it's approved.
