Repeating sections allow the creation of additional rows, but the rows inside the section are always displayed in the same order.

Would it be complex to display the repeating section in a different order? based on the order of one of the row control?

The designer would define a parameter in the rpt section that list all the controls name in one row. designer would select one of those controls, and the repeating section would be displayed in that order in display mode. That could work with dates, numbers, texts...

Alternatively, another feature could be the ability to switch the position of lines in edit mode.

Have the possibility to have dedicated JS event functions.
At the moment if you have several repeating sections, you need to check globally which control sent the event :

NWF.FormFiller.Events.RegisterRepeaterRowAdded(function () {

var currRow = NWF$(arguments[0][0]);

if (currRow.parents(".rptA").length > 0) { ... }

else if (currRow.parents(".rptB").length > 0) { ... }

else if (currRow.parents(".rptC").length > 0) { ... }

else { ... }

});

When you want to add a new row in all repeating sections, you have a cascading effect since the function will be triggered for each repeating section.
With 4 repeating sections, you have 16 executions to add 4 lines, with 7 repeatings --> 49 exectutions to add 7 lines.

It would be nice to have dedicated JS functions :

NWF.FormFiller.Events.RegisterRepeaterRowAddedrptA()
NWF.FormFiller.Events.RegisterRepeaterRowAddedrptB()
NWF.FormFiller.Events.RegisterRepeaterRowAdded_rptC()

In InfoPath I have used multiple views of a form in combination with Form Load Rules to present a separate form for users on the same list depending on a rule. One example was a separate form for the initial add item and then another view when editing. The rule would just look at a required field and see if it is empty. Another example one form was used when adding and editing the initial record. The form had a field for adding additional lines and I used Nintex workflow to add these with a different value in one field than that first record. Then when you edited any of those rows you got a different form.
I'm just wondering if this can be done in Nintex Forms for SharePoint on-prem.

Thanks - Rick

Hi,

The biggest problem with radio buttons/choice controls on Nintex Mobile is that it defaults to the native behaviour of displaying all values in a list, such that selecting the control it "pushes" the list to a new window on the stack and the only screen you see IS the list. Users then select a value(s) and the user then "pops" the window off the stack returning the user to the page with the option choices value(s) shown.

There is an alternative behaviour that can be implemented, and I have done this as an iOS developer, and the behaviour I speak of is displaying the options as a pop up rather than a stack.

The benefits are that the underlying page is still visible, and the list displayed can be minimized to the list content. This would work on both iPads AND mobiles. It's a lot more user friendly, especially when you have many choice questions, as users aren't constantly switching screens.

Could I request this change?

Regards

Chad

Because of how I designed 2 forms over 2/3 of a year ago, I need to spend extra time to perform a certain request for a client. I currently need to update 5 different choice controls with information that already exists in another list.

What leads to the issue described in the topic is that in my research to move this information out of choice controls and into a list lookup required me to set the column types to single line of text. Now, the list lookup control does support this, however one of the columns allows multiple selections, and the data in this column can exceed the maximum size capability of a single line of text column.

Since list lookups do not support multiple lines of text columns, it is possible to select more data than is supported and the form will not submit. So, it would be nice to give this kind of support to the list lookup control.