Hi @naruk89179065  In AEM as a Cloud Service, deployments are managed through Cloud Manager’s CI/CD pipelines. Each pipeline deploys a single "all" package, which contains all the application code (immutable content) intended for the /apps folder. Here’s the key point: When the PathFactory pipeline ...

Hi @ShashankJa1  Yes, when you rename a tag in the AEM Tag Console, AEM maintains a reference to the tag by its ID (namespace:path), not the display name or value.1. Does the value get automatically updated in the referenced pages and content fragments ?. Yes, but with context: What happens technic...

Hi @RainyFe    This is not an LLM-generated answer. Also, this is a normal JavaScript snippet  you should give it a try and check. I encountered something similar a few months ago, and this approach worked for me. Thanks.

Hi Sure,  @HarshVa2 The field name specified in the sort parameter must exactly match the field name defined in your content fragment model in Adobe Experience Manager (AEM). GraphQL is case-sensitive. Your query is:query {ContextList(filter: {tags: {_expressions: [{value: "content-type/story"}]}}so...

Hi @RainyFe    For this type you can use a custom data attribute like data-extension-custom and access it via the DOM with editable.selector. This method: Avoids UE interference.Doesn’t rely on undocumented features.Requires no content model changes.Is future-proof as long as DOM access remains supp...

Hi @Harsharya    Since the sort: "DisplayDate DESC" parameter isn’t sorting the results as expected in your GraphQL query, likely due to an issue with AEM’s GraphQL implementation, the best immediate solution is to fetch the data without server-side sorting and sort it client-side.  You can try this...

Hi @Mahesh_Gunaje    Raising an Approval request is the required step to transition the extension from "Retract" to "Published" status. Only after approval will the extension become live and accessible on the AEM production site.Deploying the project to the Production Workspace makes it available fo...

Hi @Mahesh_Gunaje    The key difference lies in the type of project and its deployment lifecycle: Content Fragment Extension Project: Configuration: Your app.config.yaml includes: extensions: aem/cf-editor/1: $include: src/project-folder/ext.config.yaml Nature: This is an AEM Content Fra...

Hi @Mahesh_Gunaje    It appears your Content Fragment extension, deployed and approved in the Production workspace, isn’t working in your AEM dev and UAT environments without the devMode=true parameter. This suggests a configuration step might be missing after publishing. Log in to Adobe Experience ...

Hi @Abhishek_Dubey    Adobe Experience Manager (AEM) as a Cloud Service allows you to create microsites or landing pages from custom HTML packages, and the best way is likely through site templates, which are designed for quick site creation.   Steps to Implement Create a Site Template: Package your...