Solution.xml Formatter

Paste or select a Dynamics solution.xml manifest, apply two-space indentation or collapse inter-tag whitespace, check basic XML well-formedness, and search displayed lines. Copy can use the filtered view; Download saves the complete transformed XML.

How to Use the Solution.xml Formatter

Reformat an extracted solution.xml for easier inspection; treat Validate as a basic XML structure check only.

  1. Extract solution.xml from a solution .zip, then paste it or select the file.
  2. Select Validate to check basic XML well-formedness.
  3. Use Beautify for two-space indentation, or Collapse to remove inter-tag whitespace; Expand restores beautified output.
  4. Search for publisher, version, UniqueName, or RootComponent text to display matching lines.
  5. Copy the displayed lines or download the complete transformed solution.xml.

Formatting transformation

Beautify and Collapse apply the same local XML transformation used for readable comparison of manifests: developers confirm publisher prefix, solution unique name and version, managed flag, and RootComponents before comparing packages or filing a PR.

Example

A minified <ImportExportXml><SolutionManifest>…</SolutionManifest></ImportExportXml> blob becomes indented nested elements after Beautify so Version and Publisher nodes are easy to scan.

Output meaning

  • Validation success means the XML looks well-formed, not that the package is importable.
  • Search hits are a view filter—not a patched manifest.
  • Downloaded files reflect Beautify/Collapse state for the full document.

Mistakes and limitations

  • Do not copy a searched slice back into a solution zip expecting a complete manifest.
  • Schema, layering, missing components, and environment mismatches remain your responsibility.
  • This is not a solution packager, packer, or ALM pipeline.

Privacy note

Manifest processing is browser-local with no upload. Redact or protect copied XML that reveals internal publishers, component names, or organization-specific details.

FAQ

Where do I get solution.xml?

Export a solution from Dynamics 365 / Dataverse as a .zip, extract the package, and open solution.xml at the package root (alongside customizations.xml). Both managed and unmanaged exports include it.

Does Validate prove the solution will import?

No. It only checks basic XML well-formedness. It does not validate manifest schema, component dependencies, publisher settings, versions, digital signatures, or target-environment compatibility.

How do Search, Copy, and Download interact?

Search filters displayed lines and Copy follows the filtered view. Download always writes the complete formatted or collapsed solution.xml. Processing stays in the browser.

Can I format customizations.xml here too?

The formatter is a general XML beautify/validate/search utility. You can paste other well-formed XML, but the guidance and download naming target solution.xml manifests specifically.

Will Collapse change import behavior?

Collapse removes whitespace between tags. For typical solution manifests this is usually harmless, but if whitespace-only text nodes mattered, prefer Beautify and re-test import in a non-production environment.

Does this tool edit RootComponents or dependencies for me?

No. It does not add, remove, or reorder solution components, fix missing dependencies, or bump versions. It only reformats and helps you inspect text.

Is the manifest uploaded?

No. Selected or pasted XML is read locally. solution.xml can still expose publisher prefixes, versions, and component lists—handle shared copies under your policies.