We would like to Add the "Insert" option to the "Redirect to URL" option in the Submit button settings. We would like to add a conditional URL to other forms based on what is chosen in a form drop down.

It would be awesome if we could have a past time option for the date/time action.
Just to limit entering times earlier in the day.
Similar to what is already configured for the limiting past date options.

We recently discovered a bug with the fn-IsMemberOfGroup() function in the case of an Active Directory group being added as a member of a Sharepoint group.

Sharepoint will correctly determine that users in the AD group are in the Sharepoint group, however, Nintex will not. Nintex only recognizes user group membership for users directly added to the Sharepoint group.

This creates an inconsistency in Sharepoint and Nintex, and has caused issues with using groups for business rules and permissioning logic.

The current behavior: The close button returns you to the default list view.

The desired/expected behavior:
- When form is opened in full page:
The close button redirects you back to where you came from OR redirects you to the redirect URL specific for the cancel button in the action panel settings, if available.
- When form is opened in dialog:
The close button should close the dialog.

Would like to have New Responsive Form ability to return the biggest ID or other fields.

[ ref:00D90q6Cb.5002v2vFder:ref ]

It would be useful to have the ability to hide the SUBMIT button, based on Rules. E.g. If the user selects option B, then the SUBMIT button is disabled so they can only close/cancel the form

We are unable to call the Get-QueryStringParameter function in Nintex 365 and we need to redirect our users to their respective Source URL (like the SharePoint native navigation).
In the last designer experience (NWC), the redirect URL cannot be build with references or variables.

The new responsive forms are great, but still has some limitations that older versions of controls had.
When using a lookup control, you can filter the values by searching for values by typing. It has however a 5000 items limit.
This value is hard-coded in the request, but Microsoft has implement paginated requests in their API.

This is a pity to have a search for large lists, but not large enough, please remove the hard-coded limit.

Please add a way to update the display styles for forms in display mode via the designer.

We have implemented some functionality on the Nintex form(i.e. Classic form of Office 365) using custom JavaScript code.

When we use chrome browser, JavaScript code is working fine.

But when we use the Edge browser, JavaScript code file is not loading and hence functionality implemented using JavaScript code is not working at all.

Kindly suggest if there is any workaround/solution which can help us to run the JS code in edge browser as well!

Currently Date and Time controls on Nintex Forms for O365 start with Sunday.
Unfortunately there is no possible way to change that via the Regional Settings of the SharePoint Site as that is not connected to the Date and Time Control. It would be good to have this implemented on the Nintex form as lots of users are complaining about the way it works today.

I have some lists that have hyperlink fields where I put links to salesforce and other lists. The New Responsive Form does not support Hyperlink fields and has no hyperlink control. Furthermore, these fields do not appear at all in the designer.

I think this is similar to Hyperlink Control for Repeating Section
https://nintex.uservoice.com/forums/218293-4-nintex-forms-for-office-365/suggestions/38496088-hyperlink-control-for-repeating-section

Currently it is not possible to read a value from a field inside the repeating section and display that value in another field or in another Tab/Page. Would be great if this limitation is resolved.

Lookup field is the only way to implement a cascading dropdown in Nintex. Since lookup fields doesn't support, setting a default value or a value based on rule, the same cant be done to cascaded dropdowns. IMHO this is a much needed feature for a form development tool and I wish to see this in Nintex.

Save and Continue button currently does not run the Validations (Rule and Form). In our scenario we are assigning actions to a secondary SharePoint List that needs the Item ID from the Main List. Save and Continue should run the Validations the same way as the Submit rules.

Users have complained about their browser autocomplete suggestions hiding the drop choices for a field. I explained to them this was a setting in their browser and they could just hit escape to close the suggestions from Chrome. But, it would be nice to turn off autocomplete for the form like shown here: https://www.w3schools.com/howto/howtohtmlautocomplete_off.asp

We need the ability to customize buttons on a New Responsive form. When using Tabs the form requires you to go the last tab to submit. The tabs are designed for different individuals to complete so we need to submit and close capability for each page.

There should be the possibilty to show or hide tabs within the tab navigation based on rules. This is a basic requierement in my opinion and I guess it should not be very complicated to realize it.

Regarding the user experience it is kinda confusing if there are several tabs shown within a new form for further process steps which are not necessary at this stage.