The "No response received" error when adding Power Pages website components (e.g., multistep forms, pages) to a solution, and the incomplete component inclusion with PAC CLI despite `--AddRequiredComponents`, is a known issue post-Wave 2 2025 updates—the Power Pages entities (adx_website, adx_webpage, etc.) have complex dependencies (site settings, snippets, templates) that the solution manager and CLI often fail to resolve fully due to indexing delays, API timeouts, or missing base managed solutions like MicrosoftPortalDependencies in the target environment. This breaks pipelines for production deploys. Here's the best practices and workaround:
Best Practice for Power Pages Solution Management
1. Use Deployment Profiles (Recommended for Selective Updates):
- In Power Pages Studio (dev) > Settings > Deployment profiles > New profile > Select only changed components (e.g., your 2-3 multistep forms/pages, web templates) > Save.
- Export: Deployment profiles > Select profile > Export profile (ZIP with delta changes).
- Production: Power Pages Studio (prod) > Import profile > Apply (merges without full solution overwrite; 1-5 mins vs. 20+ for full).
- Pros: Avoids "No response" (profile format skips solution layering); auto-handles dependencies like form steps/snippets.
2. PAC CLI Approach (For Automation):
- Update PAC CLI to latest (1.30.7+): Download from [github.com/microsoft/powerplatform-build-tools](https://github.com/microsoft/powerplatform-build-tools/releases).
- First, add the website (component type 10463 for powerpagesite):
]
pac solution add-solution-component --solutionUniqueName "YourSolution" --componentType 10463 --component "{your-website-guid}" --AddRequiredComponents
- Get GUID: Portal > Power Pages > Sites > Copy ID.
- For components (e.g., multistep form): Add individually:
pac solution add-solution-component --solutionUniqueName "YourSolution" --componentType 10464 --component "{webpage-guid}" --AddRequiredComponents # For adx_webpage
pac solution add-solution-component --solutionUniqueName "YourSolution" --componentType 10465 --component "{form-guid}" --AddRequiredComponents # For adx_webform
- Component types: 10463 (site), 10464 (page), 10465 (form), 10466 (template)—query via `/api/data/v9.1/solutioncomponentdefinitions?$filter=startswith(name,'powerpage')`.
- Sync: `pac solution sync` > Export: `pac solution export --path solution.zip --managed`.
- If timeout: Run with `--timeout 600` (10 mins) or chunk (add 5-10 components/batch).
3. Fix "No Response" and Missing Components:
- Target Environment Prep: Import base Power Pages solutions manually in prod/test: Admin center > Environments > Settings > Solutions > Import "MicrosoftPortalBase" and "MicrosoftIdentity" (download from [download from powerapps.ms](https://admin.powerplatform.microsoft.com/)).
- Solution in Dev: Create new solution > Add website > Add required objects (includes 90% dependencies like adx_webformstep, adx_sitebinding).
- Pipeline Config: Edit pipeline > Build stage > Export options: Managed, Include all dependencies, Skip missing components: No > Test build.
- Manual Fallback: Export unmanaged from dev > Import managed to prod > Stage: Updated (overwrites forms/templates) > Sync config in Power Pages > Sites.
4. For Your Multistep Form Scenario:
- Add: adx_webform (main form), adx_webformstep (steps), adx_website (context) > Publish in dev.
- Verify: Solution > Open > Components > Ensure multistep child records (steps, fields) are nested under form.
- Deploy: Use profiles for quick updates (avoids full solution re-import).
PAC CLI works for automation but add components in phases to avoid timeouts. If "No response" persists, check environment health (Admin center > Environments > Settings > Features > Power Pages: Enabled). Test with a simple page first.
Best Regards,
Jerald Felix
