If you encounter issues when working with your Salesforce connection in Nexadata, this guide will help you resolve common problems. We’ve broken troubleshooting into three sections:
Creating a Dataset via SOQL
Creating a Dataset via Salesforce Reports
Sending Data Back to Salesforce
Part 1: Issues with Creating a Dataset via SOQL
Common Issues and Fixes
Error: Invalid SOQL Query
Cause: The query syntax may be incorrect.
Fix: Double-check your query using Salesforce Developer Console or another SOQL testing tool before pasting into Nexadata.
Object or Fields Not Found
Cause: Your Salesforce user may not have access to the object or field.
Fix: Confirm your Salesforce profile/permission set has access to the required object and fields.
Query Returns No Results
Cause: The SOQL query filters out all rows, or "Include soft delete" was not enabled.
Fix: Adjust query filters or enable Include soft delete if you want deleted records included.
Performance Issues on Large Extracts
Cause: Extracting millions of rows without batching.
Fix: Use High-volume mode and adjust the Record Batch Size (e.g., 2000–5000).
Part 2: Issues with Creating a Dataset via Salesforce Reports
Common Issues and Fixes
Report Not Appearing in Dropdown
Cause: Report is stored in a private or restricted folder.
Fix: Move the report into a shared folder or adjust report permissions in Salesforce.
Error: Insufficient Privileges
Cause: Your Salesforce user doesn’t have access to the report.
Fix: Contact your Salesforce admin to grant access.
Dataset Loads Incorrect Fields
Cause: Fields in the Salesforce report don’t match expectations.
Fix: Edit the Salesforce report directly to include the correct fields. Then refresh in Nexadata.
Empty Dataset Returned
Cause: Report filters exclude all data.
Fix: Review filters in the Salesforce report and confirm there are records that match.
Part 3: Issues with Sending Data Back to Salesforce
Common Issues and Fixes
Error: Required Field Missing
Cause: Salesforce requires certain fields (e.g., Email for Contacts).
Fix: Ensure required fields are mapped in the Output Builder before syncing.
Error: Duplicate Value or Unique Constraint Violation
Cause: Attempting to insert a record that already exists.
Fix: Use Upsert instead of Insert, and map to a unique identifier (e.g., Contact ID, Email).
Records Not Updating
Cause: Action type is set incorrectly (e.g., Insert instead of Update).
Fix: Select Update or Upsert when modifying existing records.
Connection Shows as Disconnected
Cause: The OAuth token expired.
Fix: Click Reconnect in the Salesforce Connection setup page.
API Limits Reached
Cause: High-volume syncs can exceed Salesforce's daily API request limits.
Fix: Reduce batch size, schedule syncs during off-peak hours, or monitor Salesforce org API usage.
General Best Practices
Always test in Sandbox first – Use the Salesforce Test environment before syncing to Production.
Keep your API version updated – Use the highest supported API version for maximum compatibility.
Validate mappings carefully – Double-check your column-to-field mappings to prevent errors.
Monitor Salesforce logs – Salesforce setup audit and error logs can provide detailed error messages for failed syncs.