In the New Responsive Designer when using repeating sections the control name is replaced by a GUID which makes it very difficult to work with the XML in workflow when multiple fields and repeating sections are being used - having the control names brought through in the way that the Responsive Designer used to do would be highly beneficial.

When using the choice field control on a form the end users cannot unselect the choice they have made. E.g. User selects a choice value and then decides they do not want to answer that question they cannot untick the choice they selected. They can only select another choice, in my specific example I am using a choice control to auto calculate deductions for an inspection score and the user cannot unselect a choice to deduct points so I have had to add a choice value of 0 to remove the deduction points if they change their mind.

Hi,

At the moment Cancel button is available on the top bar and once the user clicks it, he will go to the SP list page.

I really want to restrict the user from going to the SP list page, I would like to suggest to have a Cancel button with the Submit button and there we can have a option to redirect to some other page once he clicks the Cancel button just like Submit button.

Thank you.
AK

The Nintex forms controls of Single Line Textbox, Multi Line Textbox, People, and Choice both allow for a Default value.

However, I do not see that option for a List Lookup control. It would be extremely helpful to be able to pre-select items in our list lookup.

This applies to the 'New Responsive Designer'

Hello,

new lookup function in the New Responsive Designer can't retrieve values from user fields / user columns.
Please consider to add the possibility to lookup user field values.

We would like to show document set as a page view under page section. However we were unable to do it because Page Viewer control is not available in Responsive design.

And also we would like to add new button controls along with the default controls.

Can you please check the feasibility of adding those controls.

Need a switch-like on the rules and not just a simple IF-ELSE when defining the rule conditions. Case in point, if you want to change behavior given a list of values in a Choice field managing this logic with multiple rules can become complex pretty quickly --try hiding fields based on three choices and you'll see how difficult it is to follow what the form designer wanted to accomplish.

While generating the rule, for look up fields, we can only check if it is filled or blank. But we want to create rules based on the look up value. Please find the screenshot attached.

There is Google MAP API feature in New Responsive form. I would like to request to allow users to start typing couple characters to filter and the auto complete address will drop down. Exactly like how it is in maps.google.com when user enters address. Address typo is our number 1 common human error and we would love to reduce this kind of error.

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.

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

Create a Header control to allow for a background color/image and text overlay. This can also be enabled for all Label controls. Provides an option for corporate branding.

In the designer, allow us to use the URL of an uploaded attachment as the source of the image file. That allows the user to preview the image that they've uploaded in the form, before they submit it.

Currently when you export a list form in the NRD and import into a task form all controls are disconnected. You have to manually reconnect them.

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.

In the New Responsive Form, (1) the Description font (that displays under a control) should be a tad smaller & (2) shrink spacing above the text so it's closer to control... like it was done in the old Responsive form.

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.

Currently Nintex Forms for Office 365 form variables cannot connect to people picker columns. Please add this feature.