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.

when 100% Full Hebrew Support for Nintex Forms and RTL on 2019 Version ?

I understand why converting classic into responsive is not at all feasible, however, I'd think that the opposite would be possible!

When working for clients, we will often try - whenever possible - to use Responsive. Usually with the beginnings of requirements, Responsive is feasible.

And then it hits ... "Can we ((do this thing that needs javascript))"? Can we ((do this thing that needs css))?" and we have to go and delete the entire form and recreate it in Classic.

Until responsive can do all the same things classic can, we definitely need a convert tool for it.

Thanks!

As we struggle with the same issue as described in community thread https://community.nintex.com/thread/13293-set-margin-for-print-to-pdf I would like to suggest the introduction of page margin setting capability for the print to pdf-section of the form setting page.

Currently there is no way to make an sql request control read only. We need to do this often. We pull data from our database and we don't want the person submitting the form to be able to change the data. The only way I found around this currently is to set the data type to label.

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.

The addition of versioning is great. However, it requires a separate set of notes to know what changed from version "x" to "x1".

I love the addition of the responsive designer. It would be extremely helpful if the classic designer also had the ability to create rules to set a feilds value.

Being able to add custom classes to Controls and giving the option to enable Custom Javascript are shortcommings the responsive Form version now has.
eg. Filling People Controls, Managed Metadata, Choice Fields and Lookup fields cannot be filled using Javascript now. Adding this would make the Responsive Form variant a useable candidate.
Now, without this we cannot use this Responsive variant because we need those capabilities.

When filling out long forms with numerous input fields, it would be good to show the user the progress that they made ; like a Progress bar that shows how much % of the form has been filled in and how much is left.

Enable Live publishing for Nintex Responsive forms.

I manually hacked a date time control to give greater precision than 5 minute intervals. On save, it throws a correlation error.

Given that we can ONLY bind date controls to date/time fields, could you please give us an option with more precision than 5 minute intervals? This seems like a really silly limitation.

When you use the technique for cascading drop down controls if the second control only has 1 value available set this as the default display value within the control.

Users shouldn't have to open up the second control to select the value.

A form control that provides Upload Directly to Library - which would place the file directly into the specified SharePoint Library.