RainKing Salesforce Common Connector Errors

This guide provides answers to the most common error messages that occur when pushing records from the RainKing platform to Salesforce. Click on the name of the error, and we will provide more information on the error. If the error is not listed below, please contact [email protected] for assistance from a certified Salesforce Administrator at RainKing.

Fails because of Validation Rule:

If your import from RainKing to Salesforce failed with a “Validation Exception” error it means the records for import failed to meet a validation rule in your Salesforce. To solve this error, either the fields that do not meet the validation rule should be changed, or the validation rule itself should be changed to allow these records from RainKing to be imported into your Salesforce. The specific import error can be sent to your Salesforce Admin to make adjustments in your Salesforce or with your RainKing – Salesforce mappings to allow these records to be imported.

There are two places where a validation rule error with RainKing imports can be addressed: either the validation rule itself, or with the RainKing to Salesforce field mappings. RainKing data will always come in to Salesforce in a clean, standardized format; therefore, if the validation rule can be adjusted to accept RainKing data in its standard format, then it should be adjusted to accept RainKing data. More information on Salesforce validation rules can be found here: https://help.salesforce.com/HTViewHelpDoc?id=fields_about_field_validation.htm

If the validation rule cannot be adjusted to accept RainKing data, then the RainKing-Salesforce field mappings should be adjusted to adhere to the validation rule in place. RainKing-Salesforce mappings are found in RainKing under Manage Integrations >> Salesforce >> Data Connector Setup:

Field mappings can also be found in Salesforce under the RainKing Admin tab, then select Data Mapping and the Object:

There are three fields that most commonly cause validation rule errors: Country, State and Industry. Those fields can be fairly easily manipulated in RainKing and Salesforce to adhere to your validation rules. If the field from RainKing that fails to adhere to your validation rule in Salesforce is not Country, State or Industry, then consider either not mapping this field or using a workaround. The most common workaround is to create a custom field in your Salesforce (for example, “RainKing Revenue”) then map the field from RainKing to this custom field in your Salesforce and use work-flow rules to update the correct field in your Salesforce based on the data passed to this custom field from RainKing. If the field causing the validation error is Country, this field is easily manipulated in RainKing’s Data Mapping – scroll to the Country field in the data mappings and click the icon beside that field to “Use Custom Country Mapping.”

With that, you can use a 2 character code for Country, the full spelling of the Country, or any value you choose to write in for each country. After making any changes to field mappings, make sure to scroll to the bottom of the mappings and select to Test Map, then Save Map and Activate the Map.

If State or Industry is the field causing the validation rule failure, RainKing uses installed packages in your Salesforce to “translate” these fields. These installed packages install a custom field in your Salesforce – “RK_State” or “RK_Industry” then use scoops to update the correct field in your Salesforce based on the data passed to the custom field. RainKing’s Industry Translator package and setup guide can be found here.

RainKing’s State Translator package can be found here – this package will install a custom field in your Salesforce called, “RK_State” – the State field from RainKing should then be mapped to this custom field and the package will install scoops that correctly update your State field with the full State spelling. Other fields from RainKing to Salesforce are less customizable and therefore, if they’re causing validation issues, consider either not mapping these fields or creating custom fields in your Salesforce to capture the data from RainKing.

Lead/Contact/Account Mapping not Found:

This error occurs if there is not an active data mapping found. The Salesforce Admin for your team will need to access either the RainKing Admin tab in Salesforce, or the Manage Integrations section in RainKing to access Data Mappings. Once here, they will need to click to activate the data mappings:

Transfer has Timed Out:

This error usually occurs when the Connector Service is not responding in time, or there is a connectivity issue with Salesforce. In both cases, pushing the records again should resolve the issue. You may also need to log out and log back into RainKing to reestablish connection.

Fails because of Invalid Cross Reference Key:

This error occurs if the original record has been altered in a way that no longer allows additional changes. To solve an “Invalid Cross Reference Key” error from RainKing to Salesforce, the record should be sent as a “New Record.” To do that, before selecting to “Send to Salesforce,” instead choose to “Lookup” the record in your Salesforce:

This will open a window containing that record’s information and you can use the “Search Your Salesforce Instance” button to look for any matches (you should not find any).

In the next window you’ll want to select “Send as New Record.”

You can then use the “Send to Salesforce” button as usual.

Fails because of Insufficient Access:

An “Insufficient Access” or “Read Only” error is a common cause of RainKing to Salesforce import failures. These errors mean the user does not have access to the field or object they’re attempting to write to from RainKing or that a field that they’re attempting to write to is set to Read Only. Please contact your Salesforce administrator for your team to adjust the Field Level Security for your profile. Information on how to do this can be found here: https://help.salesforce.com/articleView?id=users_profiles_fls.htm&type=0

Fails because Entity Has Been Deleted:

This error occurs when a record that was previously pushed from RainKing has been deleted from your Salesforce. The solution is to use the “Send as New Record” button.

Begin your push from RainKing as you normally would and then without using the “Detect Duplicates” button you’ll want to use the “Lookup” button next to the record receiving the error.

This will open a window containing that record’s information and you can use the “Search Your Salesforce Instance” button to look for any matches (you should not find any).

In the next window you’ll want to select “Send as New Record.”

You can then use the “Send to Salesforce” button as usual.

Fails because of Invalid Field:

This error indicates that there is an issue with that particular field in your Salesforce or that the user trying to push information to that field does not have the permissions needed to do so. Please contact your Salesforce administrator for your team to adjust the Field Level Security for your profile. Information on how to do this can be found here: https://help.salesforce.com/articleView?id=modifying_field_access_settings.htm&type=0

Fails because RKAPI is not enabled:

This error usually occurs if your team has an edition of Salesforce that does not support a direct push from RainKing to Salesforce, or if your company’s account has not enabled the RainKing for Salesforce connector. Below is a breakdown of the integration abilities you have based on your edition of Salesforce:

If you have the Professional edition of Salesforce, you can use the RainKing Search (native application) in your Salesforce instance to pull records into Salesforce. More information on how to do this can be found here:

Another reason for this error is if there was high usage in your Salesforce by other plugins or applications (not just RainKing) in the last 24 hours. Your Salesforce admin can check these limits in Salesforce under the API Requests from Setup->Administration Setup->Company Profile->Company Information>API Requests, Last 24 Hours, if the number there exceeds the MAX number in parentheses, the “API Disabled” error can occur.