dotnet build normally ends with a compact Build succeeded in 0.9s. In one terminal it printed the old format instead — Build succeeded., 0 Warning(s), 0 Error(s), Time Elapsed. The build was fine. The display wasn't what I expected, because on macOS and Linux .NET decides how to draw its output from the TERM environment variable, and mine was empty.
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.
When someone can't open an app in an environment, the Power Platform admin center can check the usual causes for you. Run diagnostics looks at one person's sign-in, license, group membership and roles, and says what to fix. This guide runs it and reads the results, including one that looks like a problem and isn't.
Before someone can open an app in an environment with Dataverse, they need a user record in that environment. Many people get one automatically, but not everyone and not in every environment. This guide adds one person by hand in the Power Platform admin center, so their first visit just works.
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.
An instant cloud flow runs when someone starts it. You don't need the designer for that: the flow's details page has a Run button that asks for the flow's inputs and starts it. This guide runs a setup flow that arrived in a managed solution, and checks the result.
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.
In an environment with Dataverse, people need a security role before they can use its data. Instead of giving the role to each person, give it to a Microsoft Entra group once, with a group team: everyone in the group gets the role, and new members get it automatically. This guide creates one and gives it Basic User.
