The Power Platform CLI signed me in without a problem, and the very next command failed: No active environment set for the current auth profile. The sign-in had created a profile with no environment attached. One command, pac env select, fixed it.
I set an environment variable's Export value to No and saved. When I opened the variable again, the switch said Yes, and the exported solution still held my SharePoint site's address. The switch can't be trusted on its own, the zip file is the real test, and the Power Platform CLI takes the values out.
The app needs two SharePoint lists with exact column names, and so far they exist only because Part 2 made them by hand. This part builds a Power Automate flow that creates both lists, their settings and all 16 columns on any site, and that can run again without changing anything.
Every SharePoint list has a Title column, and you can't delete it. When a list uses its own columns instead, the usual answer is to make Title optional and hide it from the forms and the view. This guide does that with five REST requests from Power Automate, and checks the view before changing it, so the flow can run again safely.
A list is only useful with its columns. The REST API's createfieldasxml adds a column of any type from a short XML definition, including its internal name, whether it's required, its choices and its default value. This guide adds columns from a flow, one per item of a loop, and only when they're missing.
Most of a SharePoint list's settings are properties of the list, and the REST API changes them with a MERGE request: send only the properties you want to change, and the rest stay as they are. This guide sets a list's description, attachments, version history, navigation link and search setting from a flow.
The SharePoint connector has no Create list action, but the REST API does it in one request. This guide creates a custom list from a flow with Send an HTTP request to SharePoint, and shows what a list created this way looks like, because it isn't quite the same as one created in SharePoint.
A flow that creates a SharePoint list should check first whether it's already there. Then running it twice changes nothing, and a half-finished run can simply be run again. This guide checks for a list with one REST request and a condition.
Before a flow removes something, it should check that it's there. contains() answers that: does this array include this value? This guide uses it to check whether a SharePoint view shows a column before a step removes the column from it.
Sometimes you don't need a whole Condition with two branches, just one value or another. if() does that inside an expression: give it something true or false, and the two values to choose between. This guide uses it to write a Boolean into a JSON body correctly.
