salesforce-common-errors

# Salesforce Common Errors ## Overview Quick reference for the most common Salesforce API errors with real error codes, messages, and solutions. ## Prerequisites - Salesforce connection established (jsforce or simple-salesforce) - Access to Setup in your Salesforce org - Familiarity with sObject field API names ## Instructions ### Step 1: Identify the Error Check the `errorCode` field in the API response or the exception from jsforce. ### Step 2: Match to Error Below --- ### INVALID_LOGIN — Authentication Failed ``` [{"message":"INVALID_LOGIN: Invalid username, password, security token; or user locked out.","errorCode":"INVALID_LOGIN"}] ``` **Cause:** Wrong credentials or security token. **Solution:** ```bash # Reset security token: Setup > My Personal Information > Reset My Security Token # Append token to password: password + securityToken # Verify IP is whitelisted or token is appended echo "Password format: ${SF_PASSWORD}${SF_SECURITY_TOKEN}" ``` --- ### INVALID_FIELD — Wrong Field Name in SOQL ``` [{"message":"SELECT Id, FullName FROM Account\n ^\nERROR: No such column 'FullName' on entity 'Account'","errorCode":"INVALID_FIELD"}] ``` **Cause:** Field API name does not exist on the sObject. **Solution:** ```typescript // Check available fields via describe const meta = await conn.sobject('Account').describe(); const fieldNames = meta.fields.map(f => f.name); console.log('Available fields:', fieldNames.join(', ')); // Common mistake: "FullName" vs "...