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.

Soap request on Web Request action in Nintex forms. Currently the Forms version of the Web Request action only allows Get or POST, it would be very useful if this also allowed SOAP requests like the Workflow Web Request Action does.

I recently implemented a Solution which interacts with SAP via Web Requests and unfortunately SAP is not able to process GET or POST, which means instead of being able to load the data on the form as the user goes we have had to do this in the workflow and create an additional task for the user to review the data before submitting for approval.

Here's the scenario:

List Lookup: Project.

Now, based on that project, I want to set fields to display: Project Manager; Location; Budget.

And, more importantly, I need this to work on Nintex Mobile, and offline.

Right now, I address this by using a concatenated string of all data that my List Lookup connects to, and then I RegEx out each piece.

It works, but, it's stupid, and also it looks gross. In my list dropdown I see things like "Project: 123456; Manager: Rhia; Budget: $5,000; Location: Vancouver;" -- not a good UX.

I know I can populate a dropdown with each of these items, but I don't want my users to have to go through and select it from the dropdown -- that's also bad UX. All the options in List Lookup are multi-select.

If lookup() worked on mobile, this would not be required but... since it isn't......

Can we have the option to be able to add task outcomes either in UPPERCASE or LOWERCASE and not default to the first letter being in uppercase and the rest reverting to lowercase?

Consider the below steps:

1. Navigate to workflow designer

2. Add a "Task Process" action to the canvas

3. Double-click the Task Process action to configure it.

4. You will notice that under the Task outcomes section, there are two outcomes: Approve and Reject.

5. Rename the task outcome "Approve" to APPROVE.

6. Click away from the text box and you will notice that it has changed back to "Approve"

8. Same behaviour occurs when you click on Add outcome and type DECLINE. When you click outside the text box it changes back to Decline instead

[ ref:_00D90q6Cb._5002v2Fendb:ref ]

I think it would be useful to have a built-in validation for hyperlink controls. Present behavior allows either addition of only the web address or only the text to display. When form is saved with only the web address entered, the value is used as the display text. When form is saved with only the text to display entered, no value is entered into the sharepoint field and it's as if nothing was done, no warning, no error. This is a universal requirement - that a hyperlink have a web address - and adding a product-level validation rule that threw a cannot-save error if only text to display is entered would eliminate at least some human error-induced pain. Thanks for considering this. --Courtland

I have a visitor request form and use a SQL Request Control to pull in a list of visitors. The SQL Request control is configured as a multi-select where they can pick multiple visitors for a given event. The SQL Request control will only allow me to connect to a single-line text column in the SharePoint list. Therefore the users are only able to select about 17 visitors until the form will not submit because the length of the single-line text column/field is greater than 255 characters. Please allow the SQL Request control to be able to connect to a multi-line text field so that the value can be much larger. I would also like to mention if I do not connect the SQL Request control to a SharePoint column it can grow to what seems like an unlimited size...although I know it can't be truly unlimited...but it is grossly larger than the 255 character limitation of a single-line text column. If I cannot connect the SQL Request to a multi-line text field there needs to be some way to get the value out of the SQL Request control and into the SharePoint list. I've also tried to grab the value with a Calculated Field and connect it to the SharePoint List but it also has the same limitation where it will only allow you to connect to single-line text field. So how about a multi-line calculated value field? Please, anything to get the value out of the SQL Request and into the list when it's value is much larger than 255 characters. If you need a hard limit I need to have a maximum of 2000 characters. My SQL table field is varchar(2000). This seem to be extremely limiting when a SharePoint list has the capabilities to handle a large field but the control does not utilize it's ability. Thank so much. Randy