OK - here's the code that works: <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:granite="http://www.adobe.com/jcr/granite/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" jcr:primaryType="nt:unstructu...

Hi - I'm working on the same issue. Did you ever get your code to work? thanks.

Is it possible to wrap all the components into a "multifield" component that can be repeated? I see this info in the Granite UI documentation: /libs/granite/ui/components/coral/foundation/form/multifieldMultifield component allows to add/reorder/remove multiple instances of a field. In the simplest ...

Thanks - I looked at the documentation but don't see any explanation on how to duplicate several fields into a new section using an "add section" button. Also I'm working directly in the XML code, not in the Metadata Schema Form template.

I'm updating a metadata schema and need to add an "add language" button so content authors can add additional copies of the section. Can anyone please share an example to make this happen? Thanks. 

We use VLT-RCP to sync content in the DAM across various AEM author environments. This process will sync the various paths from the source system. Once synced, the latest content is then replicated to the publish instances. However we noticed that deleted content is not synced across the different A...

It looks like we need to whitelist the following 4 URI patterns in Forcepoint to resolve the issue. (there are other javascript files besides main.js that the component is dependent on) https://documentcloud.adobe.com/dc-core/https://documentcloud.adobe.com/dc-rendition-provider/https://documentclou...

We see the following URL getting blocked by Websense on our internal network: https://documentcloud.adobe.com/view-sdk/main.jsWe’re using it to connect to Adobe to pass the client API key for the AEM component “PDF Viewer”. Is there a workaround for this issue that anyone could recommend?

We have extended the PDF viewer core component in our AEM environments. We have also created API keys for each of the domains in the Adobe Developer Console. When we set up the PDF viewer component in our STAGE author environment, we get the message "This application domain is not authorized to use ...

Hi,Please see code snippet below:<marketing jcr:primaryType="nt:unstructured" jcr:title="Marketing" sling:resourceType="granite/ui/components/foundation/section"> <layout jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/...