That's really a great new feature !

Great post!

I'm trying to work with the SQL Control but in my Insert Reference area i don't get the Named Control like you show in your images.  I only get Common, Item Properties, and Inline Functions.  Did something change since this post was made.  If so would like to know because I need to use this control on a Form to pull information out of our SQL database.

User enters an employee ID then that will pull the Name out of the DB. But with the SQL Control I cant set the Named Control as a parameter like you have.

Any information regrading that would be helpful.

Hey Kevin Kittinger​, sounds like you have the older version installed. The first cut was missing this functionality.. the ability to add dynamic options came second.. Grab the latest installer from here and update your dev/test to test it out and then your prod environment.

Product Downloads

Nintex Forms 2013 - Release Notes

Hey Dan Stoll​, we are running version 3.1.5.0. And the Product Downloads link you posted is given me a Access to this place or content is restricted. If you think this is a mistake, please contact your administrator or the person who directed you here.. Any help with this that you can provide.

Hello All!

I have the same problem with Named Controls - I'm trying to use value from External data filed as a parameter in SQL Request, but I do not see External Data field in Named Controls. I'm already update Nintex Forms to most fresh version.

Any help would be great! Thank you!

On your second SQL statement use like: SELECT City]
FROM DatabaseName]..dbo]..Cities] WHERE Country=Country

use the last 'Country' named control without ' '.

i was able to see the results when i test ran the query, but it is not showing in the form.

Hi, I don't know whether further advancements have been made but I have an issue with this current functionality.

I'm using the SQL Request control to help users search for a customer from our customer records. There's 20k+ records here so I have implemented a free text search that passes in the value of a named control in the form to the WHERE clause on my SQL. 

However, on form load, the SQL request will populate itself automatically with the full list of customers, which is slow, and then when the user does type a value in the search box, it will execute the query again, currently that cause a long running script error, which does resolve itself but is obviously not a good experience.

Is there a way of preventing the control from executing it's query until a named control is not blank?

Ok this is how I've done it....

First off I have 2 stored procs. One passing in the Search Parameter and subsequent results, and then a second to bring back data for your chosen selection from the search.

On the form I have the following.....

Single Line Text Box : String : Name - EntitySearch

SQL Request : Drop Down List : Name - EntityChoice : Parameter - EntitySearch

Calculated Value : Generic : Name - EntityChoiceCalc : Formula - EntityChoice

Example of Lookup that passes the Calc Field above otherwise it doesn't work if using the EntityChoice Field.

SQL Request : Label : Name - AdminLookup

Could be the stored proc that's the issue. Mines limits to 50 and if null or blank is passed it returns nothing.

Tony.

I ended up using some T-SQL with a variable to represent my named control and an IF statement.

DECLARE @search NVARCHAR(MAX), @sql NVARCHAR(MAX); 
set @search = 'Search';
IF (@search IS NOT NULL) AND (LEN(@search) > 1)BEGIN
        select @sql = N'With >cte_M10Search] as (SELECT * FROM *CubeDB].udbo]..dim_CustomerAccountsPrimaryAddr]
where (PartyName LIKE ''%'+@search+'%'' or AccountNumber like ''%'+@search+'%'')AND DataAreaID = ''M10'')
select * from *cte_M10Search]
where InvoiceAccount = AccountNumber;  
' 
 END
  print @sql
  exec sp_executesql @sql‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Anthony Parker, Ryan Greenaway,

I hope you can help me with my scenario. I have a text field called name and a text field called sort name in SQL as well as on SharePoint list. The way it works right now is that data is entered through legacy application. While entering data, the sort name is the sorter name of the name which is automatically set, and if duplicate it prompts users to change it. Users usually add 1 or 2 and save it, which is fine.

Now since they want this to be pushed through SharePoint since it requires bunch of approvals, everything works on insert except for sort name scenario. I had a work around to create unique sort name, but it only works 99.9% of the time, they want 100%. With the help of my DBA, she wrote a stored procedure, but it does not display anything while previewing.

and the stored procedure is as follows:

USE [database]
GO
/****** Object: StoredProcedure [dbo].[stored procedure name] Script Date: AM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

ALTER proc [dbo].[stored procedure name]

(@number = 0,@sortname bSortName )
as

set nocount on

--declare @rcode int
--select @rcode = 0, @msg = 'AP Unique'

IF EXISTS (SELECT TOP (1) 1 FROM Table WHERE NUMBER =@number and SortName=@sortname)
Begin select @sortname= @sortname + '1'
End

select @sortname

I'm struggling to understand what you're trying to do

Can you expand a little. Like I'm 5

Also I assume the SP shows the correct result when executed via SQL Management Studio and the rights to execute the SP have been granted to the Nintex Account.

Anthony Parker,

Sorry for the late reply. Yes, it executes correctly when testing from management studio and the nintex account has all the rights as well.

I am trying to use the stored procedure to look for sort name and if it is duplicate add 1 to it. The sort name comes from vendor name which is entered on the form. A calculated value picks up the vendor name that is entered and that calculated value is passes as the parameter to check on the stored procedure.