Power Platform Community Forum Thread Details

Hello,

The issue of missing forms and web templates during deployment from an unmanaged solution (dev) to managed solutions (test/prod) via Power Platform Pipelines is a common problem caused by incomplete component inclusion, dependency resolution failures, or conversion issues during unmanaged-to-managed packaging—pipelines export unmanaged as managed, but if components like forms (adx_webpage, adx_webform) or templates (adx_webtemplate) aren't explicitly added with all dependencies (e.g., site settings, content snippets), they get dropped or fail silently. This isn't a bug but a solution layering/dependency gap; pipelines handle ~80% automatically, but manual verification is key. Here's how to resolve:

Diagnosis Steps
1. **Check Solution Contents and Dependencies**:
   - In dev maker portal > Solutions > Your unmanaged solution > Open > Verify forms/templates are added (Components > Forms > Your pages/forms; Web Resources > Templates).
   - Run Solution Checker: Tools > Solution Checker > Select solution > Run > Review "Missing Dependencies" (e.g., adx_site, adx_website must be included for context).
   - Export locally: Export as managed ZIP > Unzip > Check solution.xml for <form> and <webtemplate> entries—if missing, re-add in dev.

2. **Review Pipeline Logs**:
   - Power Apps > Pipelines > Your pipeline > Runs > Select failed run > View details/logs > Look for "Skipped components" or "Dependency warnings" (e.g., "Form XYZ not exported due to missing parent adx_webpage").
   - If no logs: Enable verbose in pipeline config (Advanced > Logging: Detailed).

### Resolution Steps
1. **Ensure Complete Solution in Dev**:
   - Unmanaged solution: Add all:
     - **Forms/Templates**: Pages > Edit > Save as new form > Add to solution > Include relationships (1:1, 1:n like adx_webpage to adx_webtemplate).
     - **Site Components**: adx_website, adx_site, adx_portal (parent for all).
     - **Dependencies**: For each form/template, add required views, snippets, images (Solution > Add existing > Other > Dependencies).
   - Publish all customizations in dev before export.
   - Best Practice: Use "Include dependencies" when adding (avoids 70% misses).

2. **Fix Pipeline Deployment**:
   - Pipelines > Your pipeline > Edit > Development stage > Solution: Select your unmanaged solution > Unmanaged (for dev) > Export options: Include all dependencies > Save.
   - For test/prod stages: Set to Managed > Import options: "Overwrite customizations" On (preserves existing; merges forms/templates).
   - Run pipeline: Monitor progress—manual import if fails (export ZIP from dev > Import to test/prod manually > Stage: Managed).
   - Post-deploy: Power Pages > Sites > Your site > Sync configuration (refreshes missing UI elements like forms/templates).

3. **Workarounds if Persists**:
   - **Manual Export/Import**: Dev > Solutions > Export (Managed, Include dependencies) > Test > Import > Skip if prompts > Publish all.
   - **Split Solutions**: Separate Power Pages-specific solution (forms/templates only) > Deploy independently to avoid conflicts.
   - **Deployment Profiles** (Alternative to Pipelines): Power Pages Studio > Settings > Deployment profiles > Create > Select only changed forms/templates > Export profile > Import to target > Apply.
   - **Power Platform CLI**: `pac solution export --path solution.zip --managed` > `pac solution import --path solution.zip` (bypasses UI gaps).

4. **Prevention**:
   - Always export managed for prod (unmanaged for dev only).
   - Use version control (e.g., Git with PAC CLI) to track/rollback.
   - Test in staging: Dev → Staging (unmanaged) → Test/Prod (managed).
   - Common Miss: Web templates require adx_webpagecontent; add explicitly.

Re-add dependencies and re-run pipeline—this resolves most cases. If logs show specific missing items, share for pinpoint fix.

Best Regards,
Jerald Felix