111 posts tagged with "SharePoint"

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 =.

A manager approved an employee's response, but the employee's screen kept saying Waiting for review, even after she opened it again. Microsoft documents why: a running canvas app doesn't pick up changes other people make. The fix is to call Refresh when a screen opens, and to give people a Refresh button for when they stay on a screen.

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.

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 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.

To change an item in a SharePoint list by hand, select it, choose Edit, change the values in the Item properties form and Save. It's also the quickest way to set up test data for an app that reads the list.

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"}.

Defaults gives you a data source's default values as a record. Its main job is to tell Patch "create a new item" rather than "update this one".