Currently, Nintex Form unable to display the historic version of the SharePoint List Item. Nintex Forms can only display the most recent version of the item the user has access too.

When using Nintex Form, the user should be able to get the item historic version and not the most recent one.

[ ref:_00D90q6Cb._5009027Qcft:ref ]

Missing the ability to add buttons.

Also ability to customise buttons Save and Continue or Save and Submit -> set connected field on submit and set it’s value to something

it would be great to have a control that integrate and validate any abn entered into a control against valid abns

It would be good if you could either set the collapse functionality to collapsed by default and or apply a rule in the rules engine to collapse a group automatically.

Within the old designer, you could add a field to SharePoint - and then use within the form. The new responsive designer doesn't have this.

Workaround is to save/close - and go to the List Settings - add the field, then go back to edit the form. Would be nice to add a field "in the designer" - like with the older/previous forms designer.

According to the FAQ it's a 'Yes....but'. Without this function calculated values based on a SP lookup control is impossible.

Per a support ticket, I've been told "We do not support accessibility ( WCAG at any level or 508) currently. We are considering this, but we have no immediate plans or commitments to do this at this time."
We were told at the point of purchase that your product was accessible.
If you intend to work with higher education or government agencies, your tool should be fully accessible and meet WCAG 2.0 AA standards.

Need a connector for MS Graph API in Nintex forms for o365. This would open the ability to make calls to MS Graph for validation and creation of objects in Azure. This ability is available in PowerApps and would prefer to stick with Nintex.

Use List and Library GUID to lock onto the resource instead of display name or URL. Any changes to the display name break the form (and workflows) and should instead work similar to Flow where it locks onto objects with GUID.

Microsoft no longer supports the use of IE11 for Office 365 applications but Nintex does not support Microsoft Edge. We have to browser jump between IE11 and Edge to get our work done.

It’s great in the new responsive designer and pages. It would be even more power full if you could apply rules from the rules engine to pages example if this is ticked show page or if this is or isn’t ticket hide page

Allow the use of Nintex Xtensions in Forms

When dragging/dropping fields from SharePoint (Related List Columns) - these are ALPHA listed.

But within the field itself - the 'connect to field' list is NOT alphabetic.
Within each of the types of sections - it would be handy, when trying to find a field.

It would be nice to be able to set field values in the preview to test rules that are driven off SharePoint list columns.

When adding a field such as "Category" - it adds a field called 'Category 1' - and I have to remove the '1' from the title + name.

Is there any reason for this ?

The Nintex Form web part for SharePoint online has no configuration features. Ideally the form should be embedded on the page using the web part and just show the form. You shouldn't have to see the ribbon at the top of the screen or the grey area around the form. This way users can stay on the page and fill out a form without unnecessary scrolling or in page navigation due to pointless padding.

There is no way to insert a hyperlink control in a repeating section for responsive forms.

Allow groups to be displayed as contracted rather than expanded by default. so user works through fields in each group in turn - but isn't daunted by a long form as the expandable groups are all that shows initially