When integrating with Salesforce, various errors might occur. This guide is designed to help you understand and resolve some of the most common errors encountered during operations between Amplemarket and Salesforce.

Salesforce Integration Errors

This section addresses common Salesforce-based errors that impact the Amplemarket integration. These issues often arise due to Salesforce settings, such as API limits or object permissions, and require specific actions within Salesforce to resolve. Understanding these errors and taking the appropriate steps will help maintain a seamless integration.

Salesforce API Request Limit Reached (Salesforce Instance)

This error arises when your Salesforce instance reaches its daily API request limit, halting further data synchronization. You need to wait for the daily limit to reset or reduce API usage from other apps. It's also important to review why the limit was reached. Check Salesforce Error Logs (Settings > Integrations > Salesforce > Logging) and usage patterns to ensure API request usage is optimized.

Amplemarket API Request Limit Reached (Amplemarket Hard Limit)

Amplemarket has reached its daily Salesforce API request limit. This limit is set at 50% of your total Salesforce daily requests. The limit helps ensure other Apps connected to your Salesforce can continue operating. You need to wait for the daily limit to reset. It's also important to review why the limit was reached. Check Salesforce Error Logs (Settings > Integrations > Salesforce > Logging) and usage patterns to ensure API request usage is optimized.

Lack of Access to Salesforce Objects

This error occurs when Amplemarket does not have the necessary permissions to access specific Salesforce objects like Leads, Contacts, or Accounts. To solve this, ensure the integration user has the required permissions for these objects.

Object Permissions for a smooth integration:

To avoid permission-related errors between Amplemarket and Salesforce, ensure that your Salesforce admin configures the following Salesforce permissions:

• Read/Create/Edit on Standard Salesforce Objects - Accounts, Contacts, Leads, Tasks, Opportunities

• Administrative Permissions: API Enabled, View Setup and Configuration, Run Reports, and more.

Salesforce Push Errors

Duplicates detected

This error occurs when a Salesforce duplicate rule identifies a potential duplicate during the creation or conversion of a Lead or Contact. The rule set to trigger an "alert" halts the process, prompting the error message.

Amplemarket's suggestion is to adapt the Duplicate Rules of your Salesforce to assess the uniqueness of a Lead or Contact based only on the associated email. For Accounts, we recommend leveraging the domain as the relevant data point for accounts to evaluate uniqueness.

Generic steps to edit your Duplicate Rules:

• Identify the Problematic Duplicate Rule:
  • Go to Salesforce Setup and select Duplicate Rules
  • Search for rules related to Leads or Contacts. Common names might include "Standard Rule for Leads with Duplicate Contacts" or "Standard Rule for Contacts with Duplicate Leads."
  • Click on the rule to open and verify that the Alert Text matches the error message, e.g., "Use one of these records?" Ensure the "Alert" checkbox is activated.

• Adjust the Duplicate Rule:
  • Choose one of the following options:
    • Deactivate the duplicate rule: Temporarily turn off the rule to stop triggering the alert.
    • Modify the alert settings: Uncheck the "Alert" checkbox to prevent the rule from halting the process while still checking for duplicates.
    • Customize conditions for exclusions: Add conditions to exempt specific records from triggering the rule.

By following these steps, you can manage how duplicate detection impacts your Salesforce workflows, ensuring smoother data integration and processing.

Learn more by checking the Salesforce Help Center article on Managing Duplicate Records.

Field integrity exception

This error is commonly triggered by a mismatch between the expected data type/format and the actual value submitted, or when required fields are missing in your request.

Steps to troubleshoot this issue:

• Check your Amplemarket's Integration Settings:
  • Go to your Amplemarket's Integration Settings.
  • Review the mappings between Amplemarket and Salesforce fields. Ensure that the field types match (e.g., integers should not be mapped to date fields).

•  Verify Data Integrity:
  • Ensure that all required Salesforce fields are included in your request.
  • Confirm that all data types align with Salesforce's requirements (e.g., use ISO format for dates).
  • Utilize Salesforce's field metadata to verify the accuracy of field definitions.

Learn more by checking the Salesforce Help Center.

Cannot update converted lead

This error occurs when there is an attempt to update a Salesforce Lead that has already been converted into a Salesforce Contact and Amplemarket couldn't find that Salesforce Contact.

We recommend updating the associated Salesforce contact record directly instead of the original lead to handle changes that need to be made post-conversion. This approach ensures data consistency across your Salesforce records.

Generic Steps to Handle Converted Leads:

• Verify Lead Conversion Status:
  • Navigate to the lead record in question.
  • Check if the IsConverted field is set to true, indicating the lead has already been converted.
•  Update Related Records:
  • Instead of trying to update the converted lead, go directly to the associated contact
  • Make necessary updates on these records to reflect any new information or changes required.

By following these steps, you can effectively manage updates to records derived from converted leads, ensuring your Salesforce data remains consistent and accurate.

Learn more by checking the Salesforce Help Center.

Invalid cross reference key

This error signifies that an attempt was made to associate records using a reference key (ID) that does not exist or is incorrect.

Ensure that all IDs used for record associations are valid and correspond to existing records in Salesforce. Use Salesforce's API to query records by ID to verify existence before attempting association.

Insufficient access or read-only

The user doesn't have the required permissions or is trying to modify a read-only field. Ensure the user's profile has appropriate access rights.

Field custom validation exception

Custom validation rules are preventing the action. Review and adjust your data to comply with these rules.

Insufficient access on cross reference entity

Lack of permission to access a related entity. Check permission settings for all related records.

Invalid or null for restricted picklist

A value submitted does not match the restricted picklist's defined options. Only submit values that are explicitly allowed.

Required field missing

Your request omitted a field that Salesforce requires. Include all necessary fields as per Salesforce's documentation.

Cannot insert update activate entity

A Salesforce workflow, validation rule, or Apex trigger is preventing the action. Review custom Salesforce settings for potential conflicts.

Invalid field for insert update

Attempted to modify a field that cannot be updated or doesn’t exist. Verify field names and update permissions.

Cannot execute flow trigger

An automated process or flow cannot run, possibly due to setup issues. Check flow triggers and criteria.

Functionality temporarily unavailable

The Salesforce feature you're trying to use is currently not available. Retry later or contact Salesforce support.

String too long

Text exceeds the field's maximum length. Shorten the text to fit within the field's limits.

Request limit exceeded

You've surpassed Salesforce's API request limits. Reduce request frequency or consider requesting a higher limit.

Cannot reparent record

Salesforce does not allow changing the parent record for this object type. Select a different action.

Entity is deleted

Trying to access a record that has been deleted. Verify record IDs and retrieval queries.

Invalid query locator

Your query or session has expired. Reinitialize and execute your query again.

Server unavailable

Salesforce servers are temporarily unreachable. Attempt your request at a later time.

Unknown exception

An unexpected error occurred. If persistent, contact Salesforce support for further investigation.