Microsoft Power Platform Low-Code Services
View All Tags
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.
Power Apps works out a License designation for every app from what it connects to. Standard apps run with the Power Apps rights included in many Microsoft 365 licenses; Premium apps need a Power Apps plan. It takes a few seconds to check.
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.
You publish a new version of a canvas app, and a user who has it open still sees the old one. In the example, no update notice appeared, and even the first reload, a few minutes later, still opened the previous version. Reloading again a few minutes after that loaded the new screens.
Power Apps Studio attaches this note to an app's data sources: A Power Apps per user plan, Power Apps per app plan or Power Apps pay-as-you-go plan will be required during playback for apps with this connector. In the example, it was attached to SharePoint and Office 365 Users, which are standard connectors. The app's License designation said Standard, and a user with only a Microsoft 365 license ran it.
Counting SharePoint items with CountRows(Filter(...)) puts a yellow triangle on the screen: Delegation warning. The highlighted part of this formula might not work correctly on large data sets. The "CountRows" operation is not supported by this connector. SharePoint can't count, so the count happens in the app, on at most 500 items. The fix is to ask SharePoint a question it can answer.
A label's formula uses a variable, and Power Apps underlines it in red: Name isn't valid. 'locMember' isn't recognized. The name is spelled correctly. The variable simply doesn't exist yet, because nothing in the app creates it.
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.
