-
Notifications
You must be signed in to change notification settings - Fork 2
Portals
The Portal project type downloads Power Pages
site content to your workspace so you can edit it in VS Code and source-control it. It
uses the cross-platform Power Platform CLI (pac pages)
commands under the hood.
Steps: Prerequisites → Connect → Download a site → Edit & upload.
- The Power Platform CLI (
pac) installed (see Getting Started). - An environment that contains a Power Pages site.
- A connected environment.
Run Dataverse PowerTools: Connect Portal. The extension ensures there's a pac auth
profile for your environment (creating one from your connection if needed) and selects
it, so pac pages targets the right org.
Verify: the output log shows the environment/profile it selected.
Run Dataverse PowerTools: Download Portal. The extension lists the Power Pages sites
in the environment (pac pages list) and lets you pick one; it then downloads that
site's content (pac pages download) into a portalpublish folder in your workspace.
Verify: a portalpublish folder appears containing the site's tables (web pages,
content snippets, web templates, etc.) as files ready for editing and source control.
If no sites are found, confirm the environment actually has a Power Pages site and that your account/app can see it.
Edit the downloaded content in VS Code, then upload changes with the Power Platform CLI:
pac pages upload --path portalpublish\<site-folder> --modelVersion 2Only changed content is uploaded. For multi-environment promotion, use deployment profiles.
| Symptom | Fix |
|---|---|
| "No Power Pages websites were found" | The environment has no site, or your identity can't see it — confirm in the maker portal. |
| Connect can't authenticate | Re-connect — see Refreshing a stale connection. |
| Download picks the wrong site | Re-run Download Portal and choose the correct site from the list. |