Hi @davidef34326447,
Despite its name, the /folder.bulkassets.delete POST endpoint is not the one triggered when you delete assets via the standard DAM Admin (Touch UI) console using the "Delete" action from the toolbar. That deletion typically goes through:
POST /bin/wcmcommand
with cmd=deletePag...
Coral UI (via Granite) does not submit the values of fields that are hidden (display: none). So even if the field was filled in previously, if it’s hidden at the time of dialog submission, AEM simply ignores it.
This is not a bug — it’s how the Coral UI intentionally behaves.
Here’s how you can ...
Hi @gnaneswar88,
1. How can I implement this conditional showing/hiding of fields based on the dropdown selection within the component and multifield?Use granite:data with cq-dialog-dropdown-showhide
AEM provides the cq-dialog-dropdown-showhide mechanism using data attributes to conditionally show o...
@SudarshanV1 Can you try this?
function getTitle(editable, item, index) {
var title = "<span class='foundation-layout-util-subtletext cmp-panelselector__indexMarker'>" + index + "</span> ";
var subTitle = "";
title = title + " " + Granite.I18n.getVar(ns.editableHelper.getEdit...
Hi @olegd52630483,
What @giuseppebag is right!
The com.adobe.aem.graphql.api package is part of AEM as a Cloud Service (AEMaaCS) internal APIs. Adobe does not publicly expose all GraphQL-related APIs, especially low-level ones like QueryEndpointProvider, in the Uber JAR.These GraphQL APIs are design...
Hi @Vishal_Kagde,
The problem is that OSGi service injection (like @Reference) does not work if you're instantiating your class manually or it's not registered properly as an OSGi component.
Try the following approach to see if it resolves the issue:
Make sure your class is declared as an OSGi comp...
Hi @sreedobe,
Even though you're able to open the URL in the browser, JavaScript fetch calls from a different origin (localhost) are subject to browser CORS policy.
Chrome CORS plugin only bypasses for testing UI, not fetch requests inside code.
Assuming you are requesting from localhost: Your AEM...
Hi @RobbieRami,
It usually means:
The service is correctly configured and ready to activate, but is waiting on one or more of its required dependencies to become available.
It hasn't failed, but it can’t become "Active" because something it needs is missing — such as a reference to another service...
Community Advisor
Add a JS script in your component's cq:dialog clientlib or page-level clientlib to hook into the dialog lifecycle.Questions
5/29/25
