Hi Gokilavani, Please provide server error log file, so we can have a look. And if possible, in the browser console, can you please show the source file line number where this is failing with error message "Cannot read properties of undefined". Thanks,Pankaj Parashar

Hi Luis, The properties mentioned by you are system generated properties which are added/updated on metadata nodes by AEM on Form creation or modification, publishing. You can't alter these values. You can add custom metadata to this OOTB metadata schema and add user provided values. https://experie...

Hi Vara,Are you using foundation adaptive form or core component based adaptive form? In both the cases, a theme is applied at the form level only. A form can't have two themes applied. For your use case, you can consider the following approaches Foundation Adaptive FormYou can define a class name f...

Hi Vara,You can download it form https://repo1.maven.org/maven2/org/codehaus/mojo/exec-maven-plugin/1.6.0/exec-maven-plugin-1.6.0.jar You can refer https://mvnrepository.com/artifact/org.codehaus.mojo/exec-maven-plugin/1.6.0 for more details. Regards,Pankaj Parashar

I recommend to use the panel to fix the issue you are facing. There is no hard rule to not to add components directly to root panel, but it is good to use some design practices to achieve the intended results.By design, in the mobile view, the mobile navigation shows each title of component added di...

Hi Durga,It seems you are using a foundation adaptive form. Headless is supported by core component based adaptive form only.  Thanks,Pankaj Parashar

Hi, You seem to have added components directly to root panel. Wrap First Name and Email fields in a panel. Thanks,Pankaj Parashar

Hi Durga,You can achieve your use case using any of the following two approaches.Approach #1 - Update .env fileAssign AEM Server URL value to variable AEM_URL, e.g. http://localhost:4502 Assign Adaptive Form path value to variable AEM_FORM_PATH, e.g. /content/forms/af/testformSet variable USE_LOCAL_...

Hi @cdressler,The console error you have mentioned is not AEM Forms editor specific. This is coming from core editor, the same error can be observed when you open sites editor. This error should not have any functional impact AFAIK.Can you please provide the below details.Are you working with founda...