This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This issue occurs on a picker control, when using a SmartObject based off of a Stored Procedure as the data source.
The issue appears to be caused by having stored procedure input parameters
having the same names as columns of select statement
of the stored procedure.
K2 Labs team is currently investigating this issue.
As a workaround, you will need to modify the stored procedure to have unique input parameters different from the column names of the select statement.