We are using Sharepoint lists for various apps and solutions in my team because of the good integration with other Microsoft services, but very poor performance when connecting to Sharepoint from Alteryx has been a problem in multiple solution contexts. Alteryx reads from Sharepoint lists take a long time, and writes take forever. The very few write tools we have in production (we avoid them like the plague because their performance is awful, and we avoid writing to Sharepoint from Alteryx if there's any way at all to avoid it) are now all configured with throttling tools in front of them because we've experienced that this was simply necessary for us in order to have stable solutions that didn't break after a week or two. We have experienced repeated problems with 'list blowup' in delete and append settings, because it seemed like Sharepoint just couldn't keep up with Alteryx (the Sharepoint List Output tool seems to be 'better' at appending than deleting records, what we've seen is that lists kept being populated by large numbers of duplicates until they were growing so large that they were no longer unusable - this happened not once but multiple times, in multiple different solution contexts (...and repeatedly in some solution contexts) - and the throttling solution has eliminated the problem, but it also means that writes are even slower than they might otherwise be).
The bottom line for us is that the standard Sharepoint Connectors are simply not meeting our requirements in multiple solution contexts and solution structures involving both Alteryx and Sharepoint data are very poorly performing solutions. So either we figure out some way to better interact with Sharepoint data in Alteryx, or we either stop using Sharepoint lists or we stop using Alteryx in those specific solution structures.
But that said... might there be some third option we're not aware of, have some of the clever people in here perhaps managed to actually get decent performance interacting with Sharepoint lists by e.g. creating their own (improved) Sharepoint Connector, or ..? I'm aware that people in here will probably 'blame' Sharepoint for the problems, but even so, are there no clever Alteryx solutions to those Sharepoint problems?
