Skip to main content
Nintex Community Menu Bar

 

We are creating a solution using SmartForms where it would be very benefitial to list out 100s or even 1000s of records of only 1-2 columns in a list control or list view (with no pagination). Retrieving this data in SQL is near instantaneous, but when populating a list control or view it can take an extremely long time, sometimes upwards of a minute or longer depending on the amount of records returned. 

 

Is this just a limitation of K2 SmartForms where anything over 20 or so records is slow? Or is it possible something else is going on to cause this? Or is there any recommended work around?

Any help is greatly appreciated. 

Thank you for your response. 

 

Using native SQL execution made things much faster when retrieving simple data. However, in this specific case, I'm using a stored procedure as a list method to populate the view/control. On that front, the performance appears to be unimproved. The stored procedure isn't complicated. It's simply taking in a comma delimited list of ID's and then performing the select statement and filter the results to only those ID's. The stored procedure is needed to turn the list into a column of data so that it can be passed into an IN statement. 

 

Do you know if there is any work around that would accomplish this same sort of functionality without the huge performance drawbacks? All we need to allow the user to filter returned results on multiple values.

 

Thank you

After testing a bunch of things, I've found that limiting the number of columns returned with the stored procedure makes a huge difference in performance time as well.

Reply


Sidebar Buttons
Nintex Community Home Contact Nintex Support Check Nintex Status
Terms & ConditionsCookie settings