DocumentationExperience Cloud KCS

Content package deployment fails with DocViewParser$XmlParseException in Adobe Experience Manager

Last update: September 4, 2026

This article explains how to resolve Cloud Manager deployment failures in Adobe Experience Manager (AEM) Cloud Service caused by a DocViewParser$XmlParseException when the customFields property in a content package is not properly formatted. In Adobe Experience Manager. To fix this issue, correct the customFields property formatting in the affected content package and redeploy it through Cloud Manager.

Description description

Environment

Adobe Experience Manager (AEM) Cloud Service (all versions)

Issue/Symptoms

  • Cloud Manager deployment fails for a content package.

  • Deployment logs show an error similar to:

    code language-none 
    DocViewParser$XmlParseException: unknown type: "customFields":{"textCustomFields":[ {"fieldId":"...","name":"templateUsageRestriction",...}]

  • The failure is not visible as a stuck queue in the AEM UI, but the deployment does not complete successfully.

Cause

The .content.xml file in the content package contains a property value for customFields (such as textCustomFields) that begins with a raw JSON object (e.g., { … }) without the required {String} JCR type prefix. FileVault interprets the opening brace as a type declaration instead of a string, causing parsing to fail during deployment.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Open the affected content package and locate the .content.xml file that contains the customFields or textCustomFields property that triggers the error.

  2. For each property value that begins with a raw JSON object (for example, {"fieldId":"...","name":"templateUsageRestriction",...}), add the {String} prefix so that FileVault treats it as a string property.
    Example:

    code language-none 
    {"fieldId":"10313921169","name":"templateUsageRestriction",...}

    Change to:

    code language-none 
    {String}{"fieldId":"10313921169","name":"templateUsageRestriction",...}

  3. Save the changes and rebuild the content package.

  4. Redeploy the updated package through Cloud Manager.

  5. Verify that the deployment completes successfully in Cloud Manager and that the previous error does not recur.

recommendation-more-help
experience-cloud-kcs-help-kbarticles