API request error messages in Salesforce

This article provides a more in-depth list of known error messages that are found in the GoFundMe Pro API Requests within the Salesforce base (NPSP) integration. After the error is resolved, resync with the Data Sync tool. 

If you see any log error that you are not sure how to handle, we recommend you submit a ticket to our Care team.

FIELD_CUSTOM_VALIDATION_EXCEPTION: [Name of Validation Rule]

This means a custom validation rule is blocking record creation. Usually this requires the validation rule to be modified or deactivated. Learn more about validation rules.

To deactivate a validation rule:

1. In Salesforce, select Setup
2. Select the Object Manager tab
3. Select the impacted object
4. Select Validation Rules
5. Select the validation rule listed in the Log Error
6. Select Deactivate

Default NPSP GAU

Full message: FIELD_CUSTOM_VALIDATION_EXCEPTION: The General Accounting Unit set as default in NPSP Settings can only have amount-based, not percentage-based allocations.

The integration sets GAU allocations based on a percentage which causes an issue with the default GAU set in your NPSP Settings. This error means you should not map a GoFundMe Pro Designation to your NPSP default GAU.

CANNOT_EXECUTE_FLOW_TRIGGER: [Name of Workflow Rule, Flow, or Process]

This means a custom Salesforce process or Flow is blocking record creation. Usually this requires the process to be modified or deactivated. Learn more about Flows.

To deactivate a workflow rule:

1. In Salesforce, select Setup
2. Search for and select Workflow Rules
3. Locate the rule listed in the Log Error
4. Next to the rule, select Deactivate

REQUIRED_FIELD_MISSING, Required fields are missing: [Field Name]

This means you have a required field that our Salesforce (NPSP) integration does not fill. Typically, these are custom fields. Learn more about required fields.

To edit a required field:

1. In Salesforce, select Setup
2. Select the Object Manager tab
3. Select the Object with the required field (Ex. Contact)
4. In the menu, select Fields & Relationships
5. Select the required field listed in the log error
6. Select Edit
7. Under General Options, uncheck Required
8. Select Save

DUPLICATES_DETECTED

This means your active duplicate rules are blocking the creation of a Contact record from the processing transaction.

To resolve this, your matching or duplicate rules need to be modified or deactivated.

Learn more about Salesforce duplicate management and how to prevent duplicate Contacts.

To edit a matching or duplicate rule:

1. In Salesforce, select Setup
2. Search for and select Matching Rules or Duplicate Rules

Now, you will see a list of all the matching/duplicate rules your Salesforce instance is using. Consider deactivating some of these and retrying the Data Sync Tool.

DUPLICATE_EXTERNAL_ID

Full message includes: Upsert failed. First exception on row 0; first error: DUPLICATE_EXTERNAL_ID, GoFundMe Pro Member ID: more than one record found for external id field: [SF contact record ID, SF contact record ID, etc]: [stayclassy__sc_member_id__c]

This error occurs when the same GoFundMe Pro Member ID is on two Contact records. You must remove the GoFundMe Pro Member ID from the extra record. Once the ID is removed, use the Data Sync Tool to resync the failed transaction.

INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY

This usually happens when testing in a sandbox Salesforce org. It means the integration is trying to find a specific record that is not in the sandbox.

This issue will usually resolve itself when you switch to production as the missing record is found there.

Attempt to de-reference a null object

This usually means there is another error with a related object record. For example, if the Salesforce integration is attempting to create an Opportunity and there was an error creating a Contact, you may see this error. Also, this error may be related to custom work on your Salesforce instance. If this error appears in your sandbox instance, your sandbox could be missing the objects that the integration is trying to reference. Please make sure you are working in a full sandbox.

UNABLE_TO_LOCK_ROW

This error message happens when one record is attempting to be synced twice. More information can be found from Salesforce here.

To resolve, try to resync using the Data Sync Tool. This often works since the error is caused by other actions/processes/apps executing on the same record that the Salesforce integration is creating/updating.

FIELD_FILTER_VALIDATION_EXCEPTION

This error happens when there is a filter on a field in the Opportunity Object. The "[FieldName]" will show which field the filter is on.

To resolve, remove the filter from the field in the Object Manager.

List has no rows for assignment to SObject

This error occurs when the 'Add Contact Mailing Address as Other' setting in the GoFundMe Pro Control Panel is active in conjunction with the Salesforce State and Country/Territory Picklists feature because the picklists have not been defined in your org for the 'Other Mailing State' and 'Other Mailing Country' fields on the Contact object.

To resolve the issue, either disable the 'Add Contact Mailing Address as Other' setting in the GoFundMe Pro Control Panel Account & Contact Settings or reconfigure the State and Country/Territory Picklists from Salesforce Setup.

Invalid State Code

This error occurs when Salesforce State and Country/Territory Picklists are enabled in your Salesforce org, but the code used from GoFundMe Pro is not registered with the configured picklists.

To resolve, check the State and Country/Territory Picklists in Salesforce Setup to make sure the state/country used from GoFundMe Pro is set as active.

Invalid conversion from runtime type Lead to Contact

This error is caused by a Lead Matching Rule on the Contact object in your Salesforce Duplicate Rules. The Salesforce integration does not support this configuration.

To resolve, either deactivate the Duplicate Rule or place a condition on the rule so it does not run with the user tied to the integration.

Fundraising Page created through Reg w/ Fundraising will be fetched in order to avoid duplicates

This error occurs in skipped GoFundMe Pro API Requests when an update is made to a fundraising page and is a known issue that we are looking to fix.

As a workaround to sync updates made to fundraising pages, the Parent Campaign 'Type' field can be temporarily changed to any value other than 'Registration with Fundraising'. Then, the Data Sync Tool can be used to resync the fundraising campaigns.

Soft-credit.transferred failed

This is a false-negative error that appears in the GoFundMe Pro API Requests. It can be seen that the soft-credit was applied to the Contact from the registration purchase transaction.

No action is needed for these failures. If the amount of these API failures are becoming an issue, the records can be manually deleted in your org.

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY

Accounting Subledger

Full message also includes: caused by: npsp.ALLO_PaymentSync_SVC.PaymentSyncException: You cannot remove an opportunity allocation for a GAU that has paid payment allocations.

At this time, GoFundMe Pro does not integrate with Accounting Subledger. You can remove the default Campaign allocation, and investigate automation to correct any payment allocation issues after GoFundMe Pro/NPSP processing is complete. More information on this error can be seen from Salesforce here.

Workflow / Approval field

Full message also includes: Upsert failed. First exception on row 0; fire error CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, A workflow or approval field update caused an error when saving this record. Contact your administrator to resolve it. Name: [Name of workflow or approval field]

This error occurs when a custom workflow or approval field is blocking the API request. To resolve, use the name of the workflow or approval field in the error message to deactivate it or remove the conflict.

NPSP false negative error

Full message also includes: npsp.TDTM_Opportunity: execution of AfterInsert. caused by: System.NullPointerException: Argument cannot be null.

This error is found in GoFundMe Pro Logs regarding NPSP and means that multiple jobs are trying to access the record at the same time. If you have run the Data Sync Tool and already checked there are no failed requests in the GoFundMe Pro API Requests, then this if a false negative error, and no action is required in your Salesforce instance.

ClassySfObjectMetadata

Full message: ClassySfObjectMetadata transaction: Invalid conversion from runtime type List to Map | ClassySfObjectMetadata latestTransactionHistory: Invalid conversion from runtime type List to Map | ClassySfObjectMetadata paymentTokenHistory: Invalid conversion from runtime type Map to List

The message can be seen on API requests for transactions with a status of "Completed" and it can be ignored. The transaction did sync and the transaction ID can be searched within Salesforce to look up the corresponding Opportunity record.

Invalid picklist

Full message also includes: Message: Insert failed. First exception on row 0; first error: INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST, Name of Field: bad value for restricted picklist field: PICKLIST VALUE: [API LABEL FOR FIELD]

The error occurs because a custom picklist field is not configured correctly and is blocking the creation of records. The value causing the issue in the picklist will be shown in the message. To resolve, adjust this value in the custom field that is also named in the error message.

FIELD_INTEGRITY_EXCEPTION

The reason for this error and how to fix it is listed in the full log message. 

STRING_TOO_LONG

Full message also includes: STRING_TOO_LONG, [Field name]: data value too large: (value entered) (max length=__): [Field API name]

This error message appears when a value entered by the supporter is too long for the field. To resolve:

1. Create a case for the Care team
2. Provide the Transaction ID and the correct value for the field in question
3. When we have fixed the field value, use the Data Sync tool to resync.

No Opportunity found for id: {{transaction ID}}

This error occurs when a payout syncs to Salesforce, but the Opportunity for the transaction cannot be updated because it does not yet exist in Salesforce. This happens if the transaction failed to sync, or if it's an ACH transaction, as their payouts are sent over from the payment processor before the transaction itself is sent. 

To resolve this error, use the Data Sync tool to sync the missing transaction. You can also adjust the Payout Update Retry Attempts in the Data Processing settings so the integration will retry the API request for as many days as needed.