Hi @SmrithiG1 ,The feature is supported for core-components based Adaptive Forms, and part of the Early Access in 6.5.22 [1]. Please drop a mail to aem-forms-ea@adobe.com if you want to enable the feature on your 6.5.22 or later environment. [1] https://experienceleague.adobe.com/en/docs/experience-...

@varaande Could you help confirm if above response provides the clarity and meets your requirement.

@Saad-A You can upgrade your environment from the Cloud Manager UI. Here is the documentation for it: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/manage-environments#updating-dev-environment 

@patrickpai to confirm - are you are referring to the requirement in XFA based form (created in Designer)?

@DavidNg6 Could you confirm if you have restarted the server after installing the core-components bundle. Also, please confirm if below bundles are installed and in active state:com.adobe.aem.core-forms-components-corecom.adobe.aem.core-forms-components-af-coreNote: The class is exported by the bund...

For using Adaptive Forms core-components - we had to enable the same through the product pipeline code - enabling Forms in the archetype. With recent releases we have removed this as a mandatory requirement, and one can directly use core-components without including them in the archetype.For archety...

@crich2784 Interactive floating fields are not supported in HTML5 forms.

@Saad-A Could you confirm if the issue is resolved with the above proposal.

Hi @crich2784 ,Could you confirm is you have enabled mfDataDependentFloatingField on the profile as captured here in scripting section:https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/html5-forms/faqHopefully it should resolve the issue for you.

For more on proxy components: https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/developing/guidelines#proxy-component-patternOne needs to enable forms in AEM Archetype to get the proxy components. If you could share the archetype.properties from the repo mapped to y...