setup-solution

Creates a Dataverse publisher and solution, then adds Power Pages site components for ALM.

808|167|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/microsoft/power-platform-skills --skill setup-solution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-solution
Source: https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-pages/skills/setup-solution
Command: npx skills add https://github.com/microsoft/power-platform-skills --skill setup-solution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Power Pages sites exist as loose Dataverse records that cannot be promoted between environments until they are packaged into a solution. This Skill creates the publisher and solution, discovers every site component (pages, site languages, tables, cloud flows, bots, connection references), and adds them so the site can be exported, imported, and managed through ALM pipelines.

Core Features & Use Cases

  • Publisher and Solution Creation: Creates a Dataverse publisher with a permanent customization prefix and one or more solutions, including multi-solution splits proposed by an ALM plan.
  • Component Discovery and Packaging: Resolves environment-specific component type codes at runtime and adds website records, sub-components, site languages, custom tables, cloud flows, bots, and connection references to the solution.
  • Sync Mode: Re-runs against an existing .solution-manifest.json to diff current site inventory against the solution and adopt only newly added components, with an automatic version bump.
  • Use Case: After deploying a Power Pages site, ask to "solutionize my site" so it can be exported and promoted from a development environment to staging and production.

Quick Start

Ask the agent to set up ALM for my Power Pages site by creating a publisher and solution and adding all site components to it.

Frequently Asked Questions about setup-solution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a Power Pages site to a Dataverse solution?

Run this Skill after deploying the site at least once. It creates a publisher and solution, discovers the website record, sub-components, site languages, tables, flows, and bots, then adds them via the AddSolutionComponent API and writes a .solution-manifest.json.

What prerequisites are needed to create a Dataverse solution for Power Pages?

You need PAC CLI authenticated (pac env who returns an environment URL), Azure CLI logged in, and a powerpages.config.json with the site deployed at least once so the .powerpages-site folder contains component records.

Can I re-run solution setup after adding new pages or flows to my site?

Yes. When .solution-manifest.json exists, the Skill runs in sync mode: it discovers the current site inventory, diffs it against the solution, bumps the solution version, and adds only the missing components.

Why does solution import fail with missing dependency errors in the target environment?

Cloud flows reference connectors through connectionreference records that must also be in the solution. This Skill enumerates the connection references used by the site's flows and adds them so export and import succeed.

Does a Dataverse solution include table data when packaging a Power Pages site?

No. Solutions carry schema only: entity definitions, columns, relationships, forms, and views. Table data and records do not travel with the solution and require a separate data migration step.

Can the publisher prefix be changed after the solution is created?

No. The publisher unique name and customization prefix are permanent and are prefixed to every component logical name. The Skill explicitly asks for confirmation before creating the publisher because the choice is irreversible.