web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Pages - Administer & Monitor
Suggested Answer

Deployment Issue: Missing Forms and Templates Between Unmanaged and Managed Solutions

(0) ShareShare
ReportReport
Posted on by 2

While deploying from the development environment (which uses an unmanaged solution) to the test environment (which uses a managed solution), we consistently encounter issues where new forms, web templates, or updates to existing forms and templates are missing. It feels a bit odd and seems to be a recurring bug, whether we deploy using Power Platform Pipelines or through manual export/import.

Has anyone else experienced a similar issue or found a reliable workaround?


Categories:
I have the same question (0)
  • Suggested answer
    Jerry-IN Profile Picture
    267 on at
    Deployment Issue: Missing Forms and Templates Between Unmanaged and Managed Solutions
    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
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Coming soon: forum hierarchy changes

In our never-ending quest to improve we are simplifying the forum hierarchy…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Power Pages

#1
Jerry-IN Profile Picture

Jerry-IN 64

#2
Fubar Profile Picture

Fubar 46 Super User 2025 Season 2

#3
Michael E. Gernaey Profile Picture

Michael E. Gernaey 27 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics