Skip to main content


 

Symptoms


When attempting to create a SmartObject off of a Stored Procedure from a SQL database, there is only an Execute method available, rather than a List method.
 

Diagnoses


Because they are known to causes issues with "SET FMTONLY", K2 does not support the use of temporary tables in Stored Procedures. More information is available here:

http://help.k2.com/displaycontent.aspx?id=7349
 

Resolution

Rather than a temp table, a table variable should be used. This should resolve the issues. The above documentation has some more options as well.




 

Hi,

 

Bu the solution which is mentioned in the document (K2 SQL Server Broker: Stored Proc Requirements.pdf) for a temporary table is not feasible for the application which is running on the network.

 

When a result set is required you can create a normal table in the Database that the Stored
Procedure can write to. Then you can use two SmO calls, one to execute the stored procedure
which writes to the normal table and the second to call that table’s list method to get the results

 

This solution will work properly only on a stand-alone machine. But in case of network different users will use the same table so there are maximum chances that data will not be retrieved accurately. 

 

Thoughts......

 

Regards,

Asad Naeem

 


Hello Everyone,

 

Getting the below error while trying to cretae a start workflow rule. Any idea ??

 

"Could not find stored procedure 'Server.mGetDefaultProcSetProcesses'."


@Sanoj

Check in your K2 database first. It should be there and if it is not there then your K2 database is corrupted or someone has removed that SP. If it is there then refresh the instance in K2 testing utility for creating/updating smart objects.

Regards


Reply