I’ve embraced the use of Nintex Tables for storing information for use in workflows, and have recently banged my nose on the 1000-row limits for various Workflow actions. For one supporting application, I have to update a reference table of 1000-2000 rows, 5-6 times a day, from a report that can have upwards of about 1200 records, any number of which might have changed and require an update. These aren’t huge datasets, but when tag-teamed with the 10,000-action limit for an instance, and the number of instances in our licence, I can see that this has the potential to eat up a lot of our license capacity. For a supporting flow. Today we have a Power Automate flow that does this update, but I’d rather move it to Nintex for a variety of reasons.
I was able to figure out a workaround for my immediate situation, but it didn’t really answer the broader question of working efficiently with data in a large table, and there doesn’t seem to be much discussion on the topic so far (that I have been able to find)
Given that a table can have 200,000 rows according to the limits page (https://help.nintex.com/en-US/nwc/Content/Overview/Limits.htm) it seems that there are probably some best practices that can be developed for efficient handling of this scale of information. Suggestions?
