Passing Dynamic media renditions details from Content Fragment to 3rd party app via GrpaphQL Query | Community
Skip to main content
Level 7
October 14, 2025
Solved

Passing Dynamic media renditions details from Content Fragment to 3rd party app via GrpaphQL Query

  • October 14, 2025
  • 2 replies
  • 442 views

Hello Team,

 

AEM AMS 6.5.23 is connected to Dynamic media. Able to configure DM and once I upload images in DAM, it creates dynamic renditions details. 

Created a content fragment model, where I refer the asset(which is having rendition details). Now I need to pass the rendition details to 3rd party app via GraphQL. Can someone elaborat the details here?

Note: Sandbox name, /is/image can be shared directly with 3rd party app. Since, this will not change once its configured. Need to pass dam:scene7Name as an item in GraphQL query. 

Do I need to give option to AEM authors to select the rendition option as an drop down? I dont thing dynamic rendion name is saved along with DAM asset.

 

cc @arunpatidar  @giuseppebaglio  @santoshsai  @hrishikeshkagne @aanchal-sikka 

Thanks in advance.

Best answer by muskaanchandwani

hello @mahesh_gunaje 

Out-Of-The-Box :

The GraphQL ImageRef type in AEM 6.5 does not currently expose Dynamic Media-specific fields such as _dmS7Url or Scene7-based delivery URLs :
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/extending/graphql-api-content-fragments

These attributes are available in AEM as a Cloud Service at this time :

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql-api/content-fragments#dynamic-media-asset-delivery-by-url

2 replies

giuseppebaglio
Level 10
October 14, 2025

The dam:scene7Name property is stored in the asset's metadata at /jcr:content/metadata/dam:scene7File. To retrieve this via GraphQL:

{ contentFragmentList { items { imageField { ... on ImageRef { _dmS7Url _metadata { stringMetadata { name value } } } } } } }

Then filter the stringMetadata array where name equals "dam:scene7File" to get the Scene7 asset name.

 

Level 7
October 14, 2025

Thanks @giuseppebaglio  for your quick response.

Looks like this is not supported in AMS AEM 6.5.23, present only in AEMaaCS.

 

Thanks

Level 7
October 14, 2025

For me, even after using the latest service packs for AMS (Now, my app uses AMS AEM 6.5.23, most of the features (especially GraphQL queries. Since I am working on Dynamic media, persisted GraphQL queries) may not work(or not supported) in AMS environment, where as these features are supported in AEMaaCS.

Looks very strange to me.

cc @giuseppebaglio  @arunpatidar  @santoshsai  @kautuk_sahni 

 

muskaanchandwani
Adobe Employee
muskaanchandwaniAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2025

hello @mahesh_gunaje 

Out-Of-The-Box :

The GraphQL ImageRef type in AEM 6.5 does not currently expose Dynamic Media-specific fields such as _dmS7Url or Scene7-based delivery URLs :
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/extending/graphql-api-content-fragments

These attributes are available in AEM as a Cloud Service at this time :

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql-api/content-fragments#dynamic-media-asset-delivery-by-url