Tutorial: Use Microsoft Power Platform CLI with Power Pages

In this tutorial, you learn how to begin using the Microsoft Power Platform CLI to update a sample website's configuration.

Download and install Visual Studio Code

To connect to Power Apps portals, and to use Microsoft Power Platform CLI commands, use Visual Studio Code and the integrated terminal. The integrated terminal makes it easy to connect to the Dataverse environment and to download, change, and upload the portals configuration. You can also use Windows PowerShell instead.

Step 1. Authenticate

Before you connect, list, download, or upload any changes for a Power Apps portal, you must authenticate to the Dataverse environment first. For more information about authentication using Microsoft Power Platform CLI, go to pac auth.

To authenticate, open Windows PowerShell and run the pac auth create command using your Dataverse environment URL:

pac auth create -u [Dataverse URL]

Example

pac auth create -u https://contoso-org.crm.dynamics.com

Follow the prompts of authentication to sign in to the environment.

Step 2. List available websites

Use the pac paportal list command to list the available Power Pages websites in the Dataverse environment you connected to in the previous step.

pac paportal list

Step 3. Download website content

Download website content from the connected Dataverse environment using the pac paportal download command.

pac paportal download --path [PATH] -id [WebSiteId-GUID] --modelVersion [DataModel]

Example

pac paportal download --path c:\pac-portals\downloads -id d44574f9-acc3-4ccc-8d8d-85cf5b7ad141 --modelVersion 2

For the id parameter, use the WebSiteId returned from the output of the previous step.

Step 4. Change website content

Change the configuration using Visual Studio Code and save your changes.

For example, the default portal page shows text such as this:

This text is visible from the webpage html:

You can alter this text and save the changes:

Step 5. Upload the changes

After making the required changes, upload them using the pac paportal upload command:

pac paportal upload --path [Folder-location] --modelVersion [ModelVersion]

Example

pac paportal upload --path C:\pac-portals\downloads\custom-portal\ --modelVersion 2

The upload only happens for content that is changed. In this example, since the change is made to a webpage, content is uploaded only for the adx_webpage table.

Upload the changes using deployment profile

When working with multiple different environments, you might consider using deployment profiles to ensure the changes are uploaded to the correct environment using deployment profile.

1. Create a folder named deployment-profiles inside the folder containing the portal content. For example, if the downloaded portal content is inside "starter-portal", deployment profiles folder should be inside this folder.

   

2. Inside deployment profiles folder, create a deployment YAML file that contains the environment-specific changes. For example, development environment can be called "dev.deployment.yml".

   

3. Edit the deployment YAML file using Visual Studio Code with the following format:

   <table-name>:
   - <record-id>: <GUID>
     <column-name>: <Name>
     <column-value>: <Value>
   

   For example, the following sample YAML code updates the value for "Browser Title Suffix" from default "Custom Portal" to "Custom Portal (Dev)".

   adx_contentsnippet:
       - adx_contentsnippetid: 76227a41-a33c-4d63-b0f6-cd4ecd116bf8 # Replace with your content snippet ID
         adx_name: Browser Title Suffix # Setting name
         adx_value:   · Custom Portal (Dev) # Setting value
   

4. To upload the changes to a different environment using a deployment profile YAML file, authenticate to the target org first.

5. After authenticated and connected to the correct environment, use the pac paportal upload command to upload the content:

   pac paportal upload --path "C:\portals\starter-portal" --deploymentProfile dev --modelVersion 2

   Note

   In the above example, the deployment profile name used is "dev" after following the previous steps to create a dev deployment profile. Change the name from "dev" to any other (such as QA for "qa.deployment.yml", or Test for "test.deployment.yml") if you've used a different filename for your deployment YAML file.

Step 6. Confirm the changes

To confirm the changes made to the webpage:

1. Select Sync in the Power Pages design studio.

2. To see the change, browse to the webpage.

   

3. If you used the deployment profile example explained previously, the YAML snippet updates the value as shown in the following screenshot.

   

   The browser title suffix updated through the above change shows the change when you open the portal in a browser:

   

This concludes the tutorial. You can repeat the above steps and change the portals content for other supported tables.

Next steps

Use the Visual Studio Code extension

See also

• Microsoft Power Platform CLI
• Use the Visual Studio Code extension