Skip to main content
Nintex Community Menu Bar
Solved

Stored Procedure issue in K2 5.3 version

  • January 17, 2020
  • 4 replies
  • 149 views
  • Translate

Forum|alt.badge.img+5

Hi,

  Select query inside Stored Procedure returns Execute method in smart object instead of List method. This was working fine in K2 5.2 version, with the select query i was able to get the return property. But  when i am creating the smart object using the same stored procedure in K2 5.3 , I am not getting any return property.

 

Regards,

Kathija

 

Best answer by kathija

Hi,
I was able to resolve this issue in our DEV server. K2 database was present in different server and K2 service account did not have db_owner permission to access our application database. Once the permission was given i was able to get the stored proc in K2
View original
Did this topic help you find an answer to your question?

4 replies

  • 173 replies
  • January 17, 2020

Good day kathija


 


Please see the following.


Determine SmartObject method 'List' or 'Execute' when SmartObject was created from SQL Store Procedure: https://help.k2.com/support-services/kbt136024.


 


Best,


Sunrise

Translate

Forum|alt.badge.img+5
  • Author
  • Rookie
  • 14 replies
  • January 17, 2020
Hi Sunrise,
Thank you for the Quick reply.
I tried testing 2 of my Stored procedure using
SET FMTONLY ON;
SET FMTONLY OFF;
to check if the stored Procedure is returning schema. Both the Procedure is returning Schema. I have created SMO with return property using the same procedure in 5.2 version.
Translate

  • 2 replies
  • February 3, 2020
Kathija, K2 may not be able to understand that your stored procedure is returning an output. If your procedure code contains conditional logic (IF this then SELECT... ELSE SELECT...), it might be better to create a table variable, execute the conditional logic on the table variable, then select everything from the table variable at the end. Hope this helps!
Translate

Forum|alt.badge.img+5
  • Author
  • Rookie
  • 14 replies
  • Answer
  • February 4, 2020
Hi,
I was able to resolve this issue in our DEV server. K2 database was present in different server and K2 service account did not have db_owner permission to access our application database. Once the permission was given i was able to get the stored proc in K2
Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings