Error Handling in CRM User Mapping

Updated 

When integrating CRM systems like Salesforce with Sprinklr, it's crucial to ensure accurate and consistent user mapping. This section outlines the error handling and validation checks required during the user mapping process.

Validation Rules for Adding/Updating User Mapping

Ensure that the following validation rules are checked before adding or updating a user mapping.

1. CRM User ID Validation

The CRM User ID provided must be valid for the specified installed app.

2. Sprinklr User ID Validation

The Sprinklr User ID must be valid for the designated partner organization.

3. Email Validation

If a Sprinklr email is used via API2, it must belong to the specified partner.

4. Access Validation

The Sprinklr user must have access to the installed app. This means the app should be shared with the user.

5. Installed App Integrity

The installed app should not be deleted when using the API2 method.

6. Duplicate Mapping Check for Addition

When adding a mapping, ensure that neither the Sprinklr User ID nor the CRM User ID is already mapped.

7. Conflict Check for Updating Mappings

When updating a mapping, there should be no conflicting mappings, such as attempting to map a Sprinklr user already associated with one CRM user to another CRM user.

Additional Validations for Bulk User Mapping

When performing bulk operations, several extra checks are enforced to maintain data integrity:

1. Duplicate CRM User IDs

Ensure there are no duplicate CRM User IDs within the bulk upload file.

2. Duplicate Sprinklr User IDs/Email

Similarly, the bulk file should not contain duplicate Sprinklr User IDs/Email.

3. All-or-None Principle

Bulk operations follow an all-or-none principle, meaning if any record in the bulk upload fails validation, the entire operation will be aborted.

File Upload Specific Validations

When uploading user mappings via a CSV file, the following checks are applied:

1. Header Validation

The CSV file must include “Sprinklr User Id/Email” and “CRM User ID” in the first row as headers.

2. File Format

Only CSV files are accepted for upload.

By adhering to these validation rules and error handling mechanisms, the user mapping process in CRM integration ensures that the mappings are accurate and consistent, thus preventing potential issues with access control and data tracking across integrated platforms.