DocumentationExperience Cloud KCS

Resolving bulk export and manifest retrieval failures in Dynamic Media Classic (Scene7)

Last update: June 27, 2026

Bulk export operations in Dynamic Media Classic (Scene7) fail or appear unavailable because Scene7 has no single unified “export everything” workflow. Users expect features such as FTP export of full manifests, bulk original download from a list of filenames, or automated CSV generation, none of which exist natively. Scene7 was built as a media delivery and transformation platform, not a bulk export or archive system, so exports are constrained by per-job limits and rely on the UI, the API, or Full Publish manifests. Selecting the export method that matches the requirement — metadata, originals, filtered sets, or a migration manifest — retrieves the expected asset data.

Description description

Issue: Bulk Dynamic Media Classic (Scene7) exports fail or appear unavailable

Description

Bulk export operations in Dynamic Media Classic (Scene7) fail or appear unavailable because Scene7 doesn’t offer a single unified export workflow. Users expect FTP export of full manifests, bulk original download from a list of filenames, or automated CSV generation — features that don’t exist natively. The supported methods instead use the Scene7 UI, batch-limited export jobs (500 assets or 1 GB per job), API calls (the IPS API or submitJob), or a Full Publish to generate a manifest. These issues surface during asset migrations, cleanups, analytics, or decommissioning of legacy Scene7 accounts.

Environment:

  • AEM Dynamic Media
  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • AEM 6.5
  • Dynamic Media Classic / Scene7

Issue/Symptoms:

  • No option called “Create Job” exists to upload a list of filenames for export.
  • Users expect an FTP-based full asset export or metadata export, but no such feature exists in the UI.
  • Users need CSV/manifest data for all assets and can’t find it in the UI.
  • Users can’t bulk download originals beyond 500 assets or 1 GB per job.
  • Bulk export appears unavailable for filtered subsets, such as those containing a keyword string.

Root cause:

Scene7 / Dynamic Media Classic was designed as a media delivery and transformation platform, not a bulk export or archive system. Many expected capabilities — folder-wide export, list-based export job creation, or direct FTP export of all assets — aren’t supported. Export functionality is constrained by job limits of 500 assets or 1 GB, and full metadata export is achieved through Full Publish manifest generation or API scripts. AEM-to-Dynamic Media integrated customers must use AEM’s Export Metadata features for Dynamic Media URL extraction.

How to confirm

  1. Identify which export scenario applies: metadata-only, original assets, a filtered asset set, or a migration-level manifest. The correct workflow depends on this requirement.
  2. Confirm whether the requested capability — such as filename-list job creation or full FTP bulk export — is one of the natively unsupported features, so expectations are set correctly before choosing a method.

Resolution resolution

  1. Metadata export via Full Publish manifest (Scene7): Run a Full Publish on the appropriate Scene7 company account. After it completes, log in to your SFTP server and download the generated .txt manifest, which is named for the Scene7 company account used. The file contains all the metadata Scene7 provides.
  2. Metadata export via API (Scene7): Use the IPS APIs to retrieve asset metadata and script CSV generation. Execute the authenticated API requests to pull asset metadata; the API returns asset-level JSON or XML that you can transform into CSV. Validate that the asset count matches the expected population.
  3. Metadata export via AEM Bulk Metadata Export (AEMaaCS / AEM 6.5): In AEM Assets, use the metadata export tool to extract metadata, including Scene7/Dynamic Media URL details. Confirm the resulting CSV contains the Scene7 URL parameters.
  4. Bulk original asset export via the Scene7 UI: In Dynamic Media Classic, select the assets or folder contents, then choose File > Export. The job yields a downloadable ZIP. If the job fails, reduce the batch to under 500 assets and 1 GB, then retry.
  5. Filtered export via Advanced Search: Use Advanced Search to filter assets by keyword pattern, then select all results and export. Confirm the ZIP contents match the expected search results. If the job fails, refine the search criteria and reduce the matched set size.
  6. Export jobs via the submitJob API: Use the submitJob operation to trigger export jobs programmatically. Confirm the job appears in the Scene7 UI job monitor and runs successfully to produce output.
  7. Decommissioning a legacy Scene7 instance: Repeatedly export batches of originals using the Scene7 UI export until all assets are retrieved, confirming asset counts match what appears in Scene7. If the account is AEM-integrated, optionally use the AEM UI for selective unpublish.

Validation

  1. Confirm exported ZIPs contain all expected assets and match the counts from Scene7 UI search or folder lists.
  2. Confirm the metadata CSV or Full Publish manifest includes the correct assets, metadata fields, and URLs.
  3. For AEM metadata export, confirm the Scene7 URL fields can be constructed from the exported columns.
recommendation-more-help
experience-cloud-kcs-help-kbarticles