This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The Salesforce Input Tool has gone through some great functional iterations over the past few years. Although the deprecated version is included with every installation of Alteryx Designer (a bit hidden to find -- Right Click any tool on the "Connectors" palette and click "Show Deprecated Tools"), the most updated version requires users to download an install the .yxi in their instance of Alteryx Designer (https://gallery.alteryx.com/#!app/Salesforce-Input-Tool/59b84ccbeffc2a09d4057c43).
The newest version, developed by Alteryx, leverages the integrated Python SDK, which is seemingly more reliable than the deprecated tool. Depending on your use case you may want to use the deprecated version.
If you're like most Enterprises leveraging Salesforce, your organization most likely has hundreds if not thousands of existing reports. These reports range from basic to highly detailed depending on the use case. Salesforce reports are extremely easy for business users to construct, and can be shared and exported in various formats. It is very common for a results set of these reports to have thousands of rows. The Salesforce Input Tool as it is today will only export a maximum of 2000 rows for an existing report. In addition your report must be a report that you most recently viewed in the UI of Salesforce.
SOQL could have worked if there were not complex joins between tables. There are no current methods for finding the underlying SOQL (Salesforce Query Language) for existing reports.
If you've worked with APIs before you may have encountered a implementation called pagination. This allows for APIs to limit the amount of data that can be retrieved so that source systems are not taxed with large workloads. Instead of giving you 100,000 results in one output, an API will give you lets say 50 pages of 2,000 results per page summing up to 100,000 total results.
Like a lot of Alteryx developers, I had a deadline, and a relentless drive to solve. Could I parse out the data for 8 different reports w/ Python? After hours of Python ups and downs and multiple issues with already developed Salesforce related packages and their limitations, JSON encoding, dataframe manipulation, & super lengthy workflow execution times due to the virtual environment I gave up on Python. Remaining vigilant, I looked for other options and found https://github.com/ThyWoof/sfdc2csv. Bingo!