Documentation

Viewer presets not displaying in AEMaaCS

Last update: Mon Sep 22 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In Adobe Experience Manager as a Cloud Service (AEMaaCS) - Assets, the Viewer Presets page fails to load presets and displays a broken UI. The issue occurs due to missing or unsynced Sample and CSS assets. To resolve the issue, re-sync the assets or copy the configuration manually from a known working environment.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) - Assets
  • Feature: Dynamic Media
  • Instance: Production

Issue/Symptoms

  • The Viewer Presets list doesn’t display any items.
  • Global Navigation UI breaks specifically on the Viewer Presets page.

Cause

Missing or unsynced Sample and CSS assets prevent Viewer Presets from loading correctly and disrupt the page layout.

Resolution resolution

  1. Open the Sample Manager to re-sync the Sample and CSS assets with Dynamic Media.

    • Access:https://localhost:4502/libs/dam/gui/content/s7dam/samplemanager/samplemanager
    • Replace localhost:4502 with your actual server and port.

  2. After syncing, check if Viewer Presets are now visible in the UI.

  3. If the issue persists, manually copy the `/conf` configuration from a working environment or default configuration.

    • Ensure all required Viewer Preset nodes and CSS resources exist under /conf.
    • After copying, verify that the Viewer Presets display correctly reappear in the UI.

If the issue remains unresolved, contact Adobe Supportfor further assistance.

Best Practices and Preventive Guidance

  • Ensure all required sample assets and configuration files are deployed and synced during initial Dynamic Media setup.
  • If Viewer Presets or other configuration-based UI elements are missing, check repository paths for relevant nodes (such as /conf) and associated CSS assets.
  • Use official Dynamic Media setup and troubleshooting documentation to verify configuration integrity.
  • If asset sync doesn’t resolve the issue, manually copy the /conf configuration as a last resort.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f