
SharePoint comes in two flavors - On-Premise and Cloud. I'll show you how to do this in SharePoint. You need to create a sorted View in SharePoint and point Alteryx to that view with a record limit in the tool config to ensure you get the right data. Now, the key to getting the right data is the SharePoint View. Providing a Record Limit is optional but recommended, especially as the size of the list grows. Then, tell it which List and View to pull from. Choose your version of SharePoint and enter your credentials. So, how do we fix these problems and make the workflow more efficient? Let's start with the tool config.Ĭonfiguring SharePoint tools in Alteryx is straightforward. I asked it for 500 records and got data from 2014 - 2021. You can limit the records pulled via the SharePoint tool, but it doesn't pull from the top of the list.

My Alteryx workflow ran for 30 min before I killed it, knowing that was not acceptable.

It's been humming along both manually and in an automated form since 2014. Then, we have an Alteryx workflow that runs at night to pick up new data entered in SharePoint as part of these child processes and puts it into a spreadsheet. Submitting the SharePoint form kicks off other processes, and more data gets shuffled around. Data moves from a spreadsheet into a SharePoint form, and it works well. We automated the new Vendor setup process for our Land department using Power Automate and Power Automate Desktop. Read on to learn more about SharePoint tools in Alteryx.

This post explains how to attack these two problems to make sure you get the right data as quickly as possible. However, as you might know, the ODATA query is on the slower side, and you can't refine the query in Alteryx. In many cases, we read and write to and from SharePoint lists. Many of the automation solutions I build incorporate Alteryx with Power Automate and Power Automate desktop.
