218 posts tagged with "Power Apps"

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.

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.

A Send button shouldn't work while there's nothing to send. Set its DisplayMode to Disabled while the text box is empty, and while the save is running, so it can't be pressed twice.

Notify shows a banner across the top of the app. Use it to tell people their save worked, or why it didn't.

Now() returns the current date and time. Use it to record when something happened, such as when a response was sent; Today() gives the date alone.

To empty a column, patch Blank() into it. Microsoft's reference: Blank returns a blank value, "use this to store a NULL value in a data source that supports these values, effectively removing any value from the field" (Blank function).

A SharePoint Choice column arrives in Power Apps as a record, not as text. To write to it with Patch, send a record too: {Value: "Pending"}.