From Native form to Native Experience Cloud form

This article will take you through the things to consider and a general walkthrough of how to move your Form from Native to Native Experience Cloud (Previously known as Community).

Things to check before doing this form type migration:
 

• We have different setup for Dynamic prefill in Native than Native Experience Cloud Forms. So disable Dynamic prefill if it is enabled.

• Save for later is handled differently in Experience Cloud forms. Disable Save for Later for now, you can re-enable Save for Later after the migration.

• Captcha is different. In native regular forms we use Google recaptcha V2. In Native Experience Cloud we use our custom captcha implementation. So make sure you remove the any Captcha fields from the form and add it back after migration.

• It's worth noting that JS API syntax is different in Native Experience Forms.

Steps:

1. Go to the Form Menu page and right-click on the edit button, paste (but don’t hit enter) the URL into a new tab and then modify the URL as described in steps 2 & 3. Once edited, hit enter to access the form's structure.

2. Click on to go to Form Editor page  (i.e. https://na59.visual.force.com/apex/Visualantidote__FormEditor?id=a0Pf4000002ntivEAA)

3. Remove subpath of the link (apex/Visualantidote__FormEditor?id=) so that it becomes like this : https://na59.visual.force.com/a0Pf4000002ntivEAA

4. Change following fields (if it is not on the layout then add these to the layout)

   1. Update FormType

      1. NativeRegular => NativeLightning

   2. Check Context Type field

      1. If It should be set to Admin or User based on requirement. 

   3. Go to related 'Templates' section and click on related Template and do the same change for FormType and Context Type fields on that as well.

5. Now go to the Form Editor page as mentioned in Step 2.

6. Make a small change in the form and publish the form.