Skip to main content


 

Symptoms


We are having an issue with a smart object connected to a SQL stored procedure. The SQL just returns a table of results. When you try to filter these results either in the smartobject tester or the form we will get an error. We were not sure if you have seen this before or where this error would be coming from. I have included some screenshots of the error. We have other smartobjects tied to stored procedures that do not give any errors when they are filtered. It seems to only be this particular smartobject.
 

Diagnoses


This has been identified as a bug and fixed in latest release of K2
 

Resolution

After reviewing the SMO, it got created from a SQL Store Procedure. I was able to reproduce this on my side. To resolve this we named the Input properties different as the Return ones. This, because they were being identified as duplicate. Once we did this the SMO worked correctly.

I tried to reproduce the issue on newer versions of K2 and this has been fixed.




 
Be the first to reply!

Reply