Adobe Experience Cloud
AEM Assets metadata form import fails when permission trees grow
Diagnose a metadata form import error caused by an oversized Sling JSON response without making a broad author configuration change first.
October 28, 2026
The Assets view can import metadata forms already defined in the Admin view, but a practitioner reports that the import wizard failed in an environment with hundreds of groups and access-control entries. In the Experience League report, the request for the metadata-schema policy returned HTTP 300 when Sling's JSON result limit was reached. The form itself was not necessarily invalid.
Confirm the failing request, not just the UI error
Reproduce in a nonproduction author environment with the same group structure. Capture the browser network request, response status, and path. If the response is the policy JSON under the metadata-schema configuration, compare the number of policy nodes with the active JSON servlet limit. Preserve the request ID and relevant logs. A generic import error can have other causes; the network evidence is what narrows this one.
Fix the smallest surface
The community author raised Sling's json.maximumresults setting to get the wizard working. A responder correctly cautioned that this limit applies to JSON dumps on the author more broadly, so a large increase can raise response size and processing cost. Before changing it, review whether hundreds of individual group ACEs can be consolidated through parent groups and whether the policy tree has redundant entries. Test that access remains correct for each role.
Validate an exception before release
If permission consolidation is not viable, stage a modest servlet-limit change with the current OSGi configuration merged rather than overwritten. Confirm the import succeeds, inspect response size and author latency, and verify no unrelated JSON endpoint regresses. Keep a rollback value. Adobe's metadata-form guidance describes the supported import path; it does not prescribe this servlet tuning.
Adovo’s view
An authoring failure can be a permissions-shape problem. Raising a global limit may restore a button, but it also accepts a larger system cost. Trace the failed request first; change the permission graph when possible, and treat a broader limit as a measured exception.
