I've a form that has a sql query that brings data on the form. Once the user selects from the drop down menu, it saves it correctly. The information (on that field) can be viewed in the view mode. but if try to edit the form, the value on the sql query field is not selected. Below are screenshots of the configuration, an example of the values selected, links to the list fields and then the same form in view mode and edit mode. It's causing data entry delay as everytime they edit the form, they will have to reselect the vendor over and over. any ideas why this is happening?
The field configuration:
This shows the values for fields vendor ID and Vendor ID2, VendorID2 is the one that is supposed to be displayed on the form in view/edit mode.
This is the form in View mode, which does show the VendorID2 field, with now issues.
Once the user tries to edit the form, the selected value from the drop down list is not there, and it is a required field, so they will have to reselect everytime.
Do I need to mark the "execute in edit mode" == No? Isn't this field is to get the list of vendors from the database and make them available for selection but shouldn't not flush the existing data?
I was curious to see what if I choose to "execute in edit mode" to be == No, would do..
And here it is, it still doesn't select the value by default, but when I click on the drop down menu it shows the option for only the vendor that was selected before.
I'm encountering this same issue. I've got a SQL Request Control rendered as a multi select check box list. It's a stored procedure that uses a text box control on the form to effectively perform a free text search on the SQL table. When users select items, via a calculated value these items are stored in multi line text field so I can manipulate them a little. The raw data is saved into another field. When I reopen the form in view mode the selected items are there, but then in edit mode they are not selected and if you resubmit them then the original values are overwritten which is no good to us.
I don't believe the SQL Request Control used to work this way. I have been using the SQL Request Control with the List (Multiple-Selection) display format and it used to retain the selected values entered in the New form even when "Execute in Edit" is set to Yes. I recently upgraded to 126.96.36.199 and noticed this issue. I have submitted a support request and will update this thread when I hear back from Nintex.
I've had a response to my ticket with Nintex saying that it's been resolved in Nintex 2013.
Unfortunately I am running 2016 so can't test but would be interested to here if it's sorted.
Also, does it now retain values if executed more than once. So I have a cascading dropdown/selection controls where a user may make a selection from the second multi select control, then update their selection in the first dropdown and make more selections in the multi-select.
My theory is that it won't retain values as the query has been executed with different values therefore it cannot retain values that were selected if they aren't returned in the next query.
We have upgraded to version 188.8.131.52 and this issue seems to have been resolved. The SQL Request Control displays the saved data as expected in Edit mode.
hi Amy MacInnis & Have you done anything special other than the upgrade to make it work?
I just upgraded Nintex forms 2010 to version 184.108.40.206 and the sql selected value is still not selected when in edit mode!!
I republished the form, re-selected the value on one of the items and saved the form, reopened in edit mode and it is still not selected..