Hi @SantoshSai , Just to clarify,  question is specifically related to a project based on Adobe Edge Delivery Services, using the aem-boilerplate-commerce starter. In this architecture, we are not using Maven archetypes or traditional AEM clientlibs, so the recommendations about /apps/.../clientlibs...

Hi everyone, I'm working on a project using the aem-boilerplate-commerce in Edge Delivery Services and need to generate a sitemap-index.xml that references other sitemaps like categorias-sitemap.xml, productos-sitemap.xml, etc. Here’s an example of what I’m trying to achieve: <?xml version="1.0" enc...

hi @kautuk_sahni ,In my project it worked as follow: query productSearch($urlKey: String!) { productSearch( phrase: "" filter: {attribute: "url_key", eq: $urlKey} ) { total_count items { product { sku ...

Hello Community, I have two AEM sites (AEM as cloud service Author + Edge Delivery Service with Franklin/EDS template) set up almost identically, but I’m seeing two puzzling differences: 1. hostRoot / codeBasePath detection: function setup() { window.hlx = window.hlx || {}; window.hlx.RUM_MASK_U...

Hi @TarunKumar , Thanks for your response. Just to confirm—does the same apply to the Catalog Service as well, for example in productSearch? Best regards,Oscar

Hi Adobe Community,In my Storefront implementation, I see that the GET_PRODUCT_DATA GraphQL query for Catalog Service is defined as follows: query GET_PRODUCT_DATA($skus: [String]) { products(skus: $skus) { ...ProductFragment }} Is it possible to use a different argument (urlKey) instead of skus to ...

Hi community, We’re using the PureJS Asset Selector (assets-selectors.js) with IMS authentication in a delivery environment (delivery-pXXXXX-eXXXXXX.adobeaemcloud.com). Our setup is working well, and we’re successfully filtering assets (e.g., by dam:assetStatus). However, we would like to know: Is i...

Hi @AmitVishwakarma , I was able to achieve it using the following payload: { "siteName": "<siteName>", "branchName": "<branch>", "repo": "<repo>" } In the response JSON, I could see the origin field correctly populated as: "origin": "<branch>--<repo>--<owner>.aem.live" Following the instr...

Hi @SantoshSai , thanks so much for the detailed clarification — this really helps! I’d like to follow up on the Cloud Manager API part, specifically regarding the branchName parameter. Cloud Manager API Spec While reviewing the API documentation, I noticed that there’s no concrete example payload o...

Hi @SantoshSai , thank you for the detailed response! Just to make sure I fully understand the suggested approach: When you mention “create multiple GitHub integrations,” are you referring to: Creating separate GitHub repositories per environment (e.g., one repo per branch)?Or using the same GitHub ...