SQL List Parameter Support
Overview
This feature enables list variables to be used directly in SQL WHERE IN clauses while maintaining full parameterization support. Previously, designers had to manually construct comma-separated value lists for IN clauses.
With this enhancement, list variables can now be passed directly into SQL queries. The connector automatically expands the list into individual SQL parameters internally.
This feature is supported across all database connectors, including:
Microsoft SQL Server (MSSQL)
Oracle
IFS 10
ODBC
Only primitive value types are supported within list variables, including:
Text
Number
Boolean
Datetime
Null
Problem Statement
Before this feature, designers often had to manually build SQL statements like:
or dynamically concatenate values into query strings.
Supported Usage
01. List variables can now be used directly inside WHERE IN clauses.
Example :

Here, userIds can be primitive values, passed from a previous Assignment step or as the result of a previous Script step.
Example : userIds = [1, 2, 3]
02. Using Seq Module Results in WHERE IN Clauses
We can pass results from some Seq module functions directly into WHERE IN clauses for filtering.
These functions help transform or extract values from sequences, which can then be safely used as list parameters.
map
Use the map function to transform each element of the original sequence and pass the resulting values into the WHERE IN clause.
Just assume that you have a database table [dbo].[Language] containing multiple languages. Now, we can use the IN clause to filter the values that we want to map from the above sequence.
collect
Use the collect function to extract and flatten values from each element in the sequence. This is useful when each item contains a list of values.
Assume that you have a database table [dbo].[UserGroup] containing multiple groups. Now, we can use the IN clause to filter the values that we want to collect from the above sequence.
choose
Use the choose function to extract only non-null values from each element in the sequence.
Assume that you have a database table [dbo].[Employees ] containing multiple Employees data. Now, we can use the IN clause to filter the values that we choose from the above sequence.
Summary
map→ transforms valuescollect→ flattens nested listschoose→ filters out null values
All results can be directly used in WHERE IN clauses as parameterized list inputs.
Last updated
Was this helpful?