Publishing my flow failed with Flow save failed with code 'InvalidWorkflowRunActionName'. The message named a condition I had called Anyone left to approve? and the character it didn't accept: the question mark. Renaming both of the flow's conditions without one let it publish.
Publishing my flow failed with The input parameter(s) of operation 'Ask_the_manager' contains invalid expression(s). The expression was one Power Automate had written for me, from a token I picked. The cause was an apostrophe in the name of the action it read from, Get the employee's manager. Renaming that action and picking the token again fixed it.
Power Automate wouldn't save my new flow. A red banner said Should at least contain one trigger and one action, and the flow had only its trigger. A flow needs at least one action before it can be saved, so I added its first real step, and Save worked.
The first time I sent this site's URLs to IndexNow, it answered 403 with SiteVerificationNotCompleted, though the key file was live and correct. Five minutes later, the same request went through.
People can log their overtime; this screen shows them what they've logged. It lists a month of their entries with a status badge on each, adds up the month and each Monday-to-Sunday week, moves between months, and lets them correct an entry until it's approved, by opening it on the Log Overtime screen.
Power Apps Studio can show what a formula returns without running the app. Select the formula's text in the formula bar, and a strip under it shows the formula, an equals sign and the result, with the result's data type beside it. It's the quickest way to check a formula while you write it.
A SharePoint view can show a total under a column: select the column's heading, then Totals and a calculation such as Sum. In a grouped view, each group gets its own total, and the list gets one at the bottom. Save the view to keep it.
Grouping puts a list's items under a heading for each value of a column, such as each month, with a count of the items in each group. Select the column's heading and Group by it, then Save view as to keep the grouping. For a second level, such as month and then person, use Edit current view.
Requests should be easy to correct until someone approves them, and fixed after that. In a gallery, give each row an Edit button whose Visible is ThisItem.Status.Value <> "Approved": pending and rejected rows can be opened, approved ones can't. When an edited item is saved, set its status back to Pending, so the change is approved too.
A check for clashes or duplicates that works when adding an item finds the item itself when you edit it. The fix is to skip that item, but SharePoint can't run ID <> x on its ID column, so put it in the query and nothing is delegated. Instead, let SharePoint find the matches with a query it can run, hold them in memory with With, and skip the edited item there.
