Hi @SixMu AEM Content Fragment Models don’t support native conditional fields.Create both fields (fuelType, batteryPower).Add help text to batteryPower:“Only fill if fuel type = Electric.”Add a clientlib for the fragment editor and use JS to show/hide the field:(function ($, document) {
$(document...
Hi @sameryadav For AEM EDS + SAP Commerce, Adobe’s recommended pattern is:Use a backend integration layer (e.g., Adobe I/O Runtime or App Builder service) to prefetch SAP Commerce product data and inject it into the HTML content during Edge Delivery build or delivery.This ensures:No client-side call...
Hi @Ajay_KR It looks like the issue is with the GraphQL schema from the commerce backend, not AEM. The IntrospectionQuery response likely has missing or mismatched fields that prevent AEM from triggering further product/category queries.Please compare the schema with the working commerce instance a...
Hi @SudarshanV1 data-sly-resource just renders another resource at runtime.It doesn’t create an editable node structure inside your current component.Because of that, in the editor, authors don’t see a "real" component instance they can copy/paste – they just see an include.Use a ParsysInstead of ha...
Hi @FabianAl1 HTL compilation in AEM occurs at build time in the ui.apps module.ui.apps module does not automatically include core classes unless declared as a dependency.Your PlatinumHeader class is in core, but ui.apps does not see it at compile time unless the Maven dependency is configured.That’...
Hi @YAMINIK1 In AEM Edge Delivery Services (EDS), content can appear in Preview or Live environments even if you don’t see a YAML configuration in the repo because not all EDS setups require a YAML file for mountpoints or content sources. Here’s why:Content Source in EDSEdge Delivery Services can f...
Hi @aldoc77148901 CIF doesn’t provide PDP, PLP, or Cart templates — you must create your own AEM page templates. Each template should have a pageType property (e.g., product-page, category-page, cart-page) that the Product Recommendations component reads to apply the correct recommendation rules. Be...
Hi @SanaQu Validate locally before deploying: Deploy your index definitions into the AEM SDK and use the Explain Query tool (/libs/granite/operations/content/diagnostics/query.html) to confirm the query plan is picking up your index. This avoids wasted Cloud Manager runs.Use DEBUG logs for deep vali...
Hi @arunpatidar I tried the same approach that was suggested and it works conceptually, but I’m running into a version issue on my side. I’m checking compatibility for my AEM setup — once I sort that out, I’ll update here.Regards,Karishma.