Duplicate components added when including Power Pages site in solution

(2) Share

Report

Posted on by omkarsupreme

I’m currently deploying a Power Pages site and noticed that when I add the site to a solution, its components are getting duplicated.

Is this expected behavior in Power Pages, or could I be missing some configuration or steps?

Has anyone faced a similar issue or found a way to avoid these duplicates?

AND Got one more error

Import failed: The attachment is either not a valid type or is too large. It cannot be uploaded or downloaded.

Categories:

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 1,703 on at

Like (0)

Report
Copy link

Link copied!

The duplication of components when adding a Power Pages site to a solution is a known behavior due to how portal data (like web pages, templates, and

snippets) is stored and deployed.

It often occurs because of missing dependencies, repeated imports, or mixing managed and unmanaged changes.

To avoid this, ensure full site inclusion in solutions, avoid manual edits in target environments, and use managed solutions with deployment profiles.

The attachment error is typically caused by large or unsupported files stored in Dataverse (such as web files or annotations).

The best approach is to reduce file size, move large assets to external storage like Azure Blob, or re-export the solution after removing problematic files.

Was this reply helpful? Yes No
Suggested answer

Valantis 3,958 on at

Like (1)

Report
Copy link

Link copied!

Hi @omkarsupreme,

For the attachment import error: this is almost always caused by web files stored in Dataverse (images, PDFs, CSS, JS bundles) pushing the solution zip over the 32MB import limit. The fix is to move large static assets out of Dataverse web files and host them externally (Azure Blob Storage with a CDN, or even SharePoint), then reference them via URL in your pages instead of storing them as web files in the solution.

For the duplicate components: can you clarify what you mean by duplicated? There are two common scenarios:

1. The same web page or template is showing up twice in the solution component list when you added the site
2. After importing into the target environment, you see duplicate records (two versions of the same page)

The most common cause of scenario 1 is that the site components already exist in the Default Solution as unmanaged customizations, and when you add the site to a new solution it picks them up again. The fix is to make sure you are working from a single solution and not mixing unmanaged Default Solution components with your custom solution.

For scenario 2, it usually means the solution was imported more than once without proper managed/unmanaged layer handling. In that case, delete the duplicate records directly in the target environment via the Power Pages design studio or Dataverse, then re-import.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

Haque 2,182 on at

Like (2)

Report
Copy link

Link copied!
Hi @omkarsupreme,

It often happens due to missing dependencies, repeated imports, or mixing managed and unmanaged changes. To avoid duplicates:

Let's make sure to include the full site and all related components in the solution when adding it.

Wisely avoid manual edits to portal components in the target environment after import.

Use managed solutions with deployment profiles for consistent deployment.

Add dependent Dataverse tables explicitly if they are not automatically included.

Regarding the import error "The attachment is either not a valid type or is too large," this typically occurs when the solution contains large or unsupported files (e.g., web files, annotations) that exceed Dataverse size limits or are incompatible. To resolve this:

Identify and remove large or unsupported attachments from the solution (if there are any).

If possible, move large assets to external storage like Azure Blob Storage or any CDN.

Export the solution as unmanaged and unpack it with Solution Packager to find problematic files.

Rebuild the solution without problematic files before import.

Verify environment registration and pipeline configuration if using deployment pipelines.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No