Microsoft Power Apps Canvas Apps, Power Fx Formulas, and Controls
View All Tags
Every screen and flow of the Overtime Timesheet app reads or writes three things in SharePoint: a list of departments and their approvers, a list of overtime entries, and a library for payroll's monthly workbooks. This part builds them, and the site they live on, column by column and setting by setting.
Many teams still record overtime in a shared Excel workbook: who worked, when, why, and who said yes. This series replaces it with a Power Apps app on SharePoint. Staff log overtime in a few taps, the hours are calculated and totalled for them, each department's approvers approve it in Teams or Outlook, and payroll gets a monthly Excel workbook and a Power BI report. Everything runs on Microsoft 365.
Thirteen parts planned, built, packaged and installed the Career Development Plan app. This last part walks through the finished app as an employee and as a manager, then gives you a checklist for running it for real, what it doesn't do, and every guide the series produced.
Part 12 produced the release files. This part installs the two managed ones the way a buyer would: in a new environment, on a new SharePoint site, with nothing carried over from where the app was built. Then a manager and an employee use it.
Environment variables keep a solution's settings apart from what uses them: which SharePoint site and lists an app reads, for example. When a solution's variables arrive without a value, the import asks you for them, so the same solution can point at a different site in every environment. This guide fills them in during the import, and in a settings file for the CLI.
Importing is how a solution gets into an environment: you upload the zip, Power Apps shows what's in it, asks for anything it needs from this environment, and installs it. This guide imports a managed solution in Power Apps, then does the same with the Power Platform CLI.
Everything you create or import in Power Apps lands in the environment shown in the header. Before you import a solution, build an app or add a table, check that it's the right one, and switch if it isn't. It takes two clicks.
A trial environment is a free, separate Power Platform environment with its own Dataverse database, for 30 days. It's the cheapest way to test installing a solution somewhere other than where you built it. This guide creates one in the Power Platform admin center, limited to one security group.
A Power Apps trial gives your account, for 30 days, what a Power Apps per user plan includes, and Microsoft requires it before you can create a trial environment, even if you're an admin. This guide starts the trial from the page Microsoft links to, and shows what changed afterwards and what didn't.
A manager opened a shared app in a new trial environment and got You can't open apps in this environment. You are not a member of the environment's security group. He was a member. The cause is how trial environments add people, and the fix is to add them to the environment yourself, or have them open the app again.
