Form Designer allows you to create and manage advanced dynamic forms compatible with the new Modern interface of SharePoint. Forms generated by the Designer contain features and capabilities matching or exceeding the classic forms. Both classic forms and modern forms will continue to be available and you can choose the kind most appropriate for your project.
Note: Once a modern form is applied to a list or library, it replaces the classic form.
The modern forms currently have the following limitations:
- No support for custom column types from 3rd party vendors (not planned)
- No support for special list types (recurrence in calendars, surveys, support is planned in the future)
- Forms not synchronized with left side navigation (technically impossible)
- Users who will be publishing modern forms through the Forms Designer will require Design permissions on the list to be able to publish their forms.
- Users who will be using forms need to have at least Read permissions to the Site Assets and Site Pages libray (for Infowise Ultimate Forms below version 1.4.0.0)
NOTE: If your Tenant/sites has upgraded to the new Infowise Ultimate Forms version 1.4.0.0, you will no longer require the Read permissions for regular users on the Site Pages library on any new forms or re-Published modern forms. If you still have Modern Forms published from before the upgrade you will still need the Read permissions for regular users until you republish all forms on the site.
NOTE: on-premises customers -
- Form designer can be used on SharePoint 2016 and up.
- Dialogs are not supported in Form Designer forms.
- Turn on multiple metadata formats see our On-Premise installation prerequistes for the from here. Prerequisites (last two items)
- Make sure .json is not a blocked file extension in your environment. You can specify what file types are blocked in Central Administration. The file type is already allowed in Office 365 and doesn't require additional steps.
NOTE: Modern Forms are not supported by Publishing sites as they are missing the default libraries that our modern forms are expecting to write too and have specific workflows and permissions that can block the modern forms from publishing properly.
For more information and examples on this topics follow these additional resource links;
- Go to the Blog page, enter "Form Designer" in "Search Blog..." for articles on this topic.
- Go to Tutorial pages, click on any of the tutorials of this topic "Form Designer".
Also, to dive deeper into the user interface functionality follow the links below: