At present when a form is submitted the people picker control is validated on user login. Can this be changed so the control is validated using Email address instead of the login name.

Would like the ability to clear unconnected fields on a Nintex Form when the form loads. Some customers have the requirement not to preserve form data to a unbound field on the form.

Currently the Nintex Mobile App doesn't display the Radio buttons, instead it shows the options as a drop down list.

We have built a QA process form which shows a poor design without Radio buttons.

Please include the Radio buttons in the Nintex Mobile App.

Thanks

This would be so useful and time-saver if we could copy control from one form to another form. Also, it should be possible that we could import a complete form let's say source form, into another form i.e. destination form while older controls in destination form are not lost. For this, user should be able to import a form in a panel sort of thing in another form.

Ability to configure the attachment control to prevent users from deleting existing attachments

Would like to have the ability to toggle if users can remove rows in a repeating section using a runtime function and a named control. Currently on both classic and responsive, nintex forms only lets you use an expression where you can use inline functions and item properties.

What could also work is perhaps having the abillity to hide the "x" in the repeating section.

Use case could be a process where users add comments or data to a form but should not delete other peoples data.

Nintex Administration --> Form Controls

Missing Ability to remove /restrict some of form control actions based on usage like we have workflow actions for workflows.

When the repeating table control is used and only one table is displayed, the X delete button is still visible although its functionality is disabled and users attempt to click it. Have the X delete button appear when there are 2 or more tables.

The ability to Restore a deleted Form from the recycle-bin.
Forms deleted from the Nintex UI are removed completely from the system with no way to recover, except from a back-up.

If we could include the option to include only unique values when building a lookup control it'd be swell!

I.e. I have a list of Departments with their corresponding Group. Each Group has multiple Departments, so there are multiple lines of each Group in the list. I want to be able to show only the unique values for Group when I build a lookup!

If the web request control is not connected to ID, when the user change the list column value via Quick Edit, the new value will not able to bound into the Nintex Form due to missing ID.

Lotus Notes Xpages and Lotus Notes forms allow you to design a "subform". This is for when you have common sections across a number of forms. Design it once then just place it on the form where needed.

Can we get such a feature in Nintex forms? I would imagine it would be used where you have content types inheriting from other content types. The parent content types should have the ability to create one or more "sub forms" that can be placed on child content types where needed.

Currently there is no way, that I'm aware of, to restrict users who have full control over their site from using Nintex forms. We would like to restrict users from using Nintex unless they have been properly trained. There should be some way to use AD accounts to allow only certain users the ability to design forms.

At the moment we can develop custom controls using SharePoint Farm Solutions.

It would be amazing if we could develop custom controls using SharePoint Framework for that, so we can use only client-side code and be aligned with SharePoint best practices.

SP2013 & 2016.

We are very happy to have received Attachments in Repeating Sections - this is a great advancement - however, the JavaScript we were using previously is not functional in these scenarios.

We require a way - in all cases - to count the number of attachments. We may have multiple attachment controls on a form, and they may or may not be in repeating sections.

Please add this functionality as soon as possible so we can stop using JavaScript for the old forms, and so we have a way to handle Repeating Section attachments!

Currently the SQL Request Control is able to capture existing list column value when open in edit mode in List Item form, but in Task form it is not pre-populating the original values from the list column. This is the major drawback when we use multi-level approvals with SQL Request control.