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.
When using the Salesforce Input tool, the following error is seen at run-time:
400: Bad Request
This may only occur on some tables
It fails almost immediately after the workflow starts running.
It may also been seen on the Salesforce Credentials screen along with the error:
invalid_grant: authentication failure
Salesforce Input tool
Version 4.0 or 4.1
Confirm where you are seeing the error. If it is on the Salesforce Credentials configuration page when you click Connect, and you see "invalid_grant", please see Solution B.
Otherwise, validate the query to get a more verbose error log.
1. Use the Query Builder option (this is the default option) and select the Table and Output Fields you want to read in.
2. Change to the Custom Query option and click the Validate button:
3. If you receive the error: "OPERATION_TOO_LARGE: exceeded 100000 distinct ids", see Solution A.
The data you are attempting to pull is too large to be returned in one call based on the Salesforce API limits used by the Salesforce Input Tool. Limit the number of results returned by modifying the WHERE Clause (SOQL) in the tool's configuration:
Please see the Additional Resources section below for a guide on SOQL (Salesforce Object Query Language). Here are some suggestions:
Try limiting date fields by relative dates :
CreatedDate = THIS_YEAR
Try limiting a string field to a certain value:
You can also combine conditions with logical operators like AND & OR:
Name='SFDC Computing' AND NumberOfEmployees>25
For more advanced comparisons, you can perform fuzzy matches by using the LIKE operator. For example, you can retrieve all accounts whose names start with SFDC by using this condition:
WHERE Name LIKE 'SFDC%'
- The % wildcard character matches any or no character. The _ character in contrast can be used to match just one character.
The credentials are incorrect. Please confirm your Username, Password, and Token are correct.
Salesforce Knowledge Base - Write SOQL Queries
Salesforce Knowledge Base - Reset Your Security Token
No Lua script was found
When reading in from a database, the following message is seen:
Info: Input Data (n): No Lua script was found for corresponding ODBC driver.
Windows Operating System
ODBC database connection
This message indicates that you are connecting to a database, and no Lua script was found. This is expected when you are connecting to a database that does not work out of the box with Alteryx. Please note this is a message and not an error or warning; it will in no way prevent your workflows from executing successfully if you are not using a custom Lua script.
To support new ODBC drivers that Alteryx has not validated/tested, you can create a custom Lua script that will map driver and database data types to Alteryx types. To learn more about this (and find sample Lua scripts) please see the documentation Customizable ODBC Driver Connections found in: %LOCALAPPDATA%/Alteryx/bin/RuntimeData/ODBC