Resolve Scene7 asset name discrepancies across AEM environments for PDF files
PDF assets have different Scene7 asset names across AEM environments due to variations in PDF processing settings. To ensure consistency, verify and align the PDF processing settings under Dynamic Media configuration across environments.
Description description
Environment
- Adobe Experience Manager (AEM) Managed Services Support
- AEM v6.5 and AEMaaCS
- Cloud Manager
- PAT_ConsoleBuilds
Issue/Symptoms
In some cases, the same PDF file uploaded to different AEM environments (for example, development and production) may result in differing dam:scene7Name values:
- Development environment:
pdf-replace-testpdf - Production environment:
pdf-replace-test
This discrepancy occurs even though both files were uploaded with the same asset name (for example, pdf-replace-test.pdf).
Custom scripts or integrations expecting a specific naming convention can encounter errors, causing delays in asset processing, content publication, or approvals.
Resolution resolution
Cause
-
Differences in
dam:scene7Namevalues is caused by variations in PDF processing settings between environments. For example,- Development environment: Process set to Thumbnail.
- Production environment: Process set to None.
-
Difference in the impact of settings on names:
- When a PDF is uploaded in an environment where the process is set to Thumbnail, Scene7 generates a thumbnail image and appends PDF to the file name.
- When a PDF is uploaded in an environment where the process is set to None no thumbnails are generated, and no modifications are made to the file name.
-
Available options for PDF Processing:
- Rasterize
- Thumbnail
- None
Solution
To ensure consistent behavior across environments, verify and align your PDF processing settings under Dynamic Media configuration for all relevant instances. Refer to PDF tab in the Configure Dynamic Media General Settings Guide.