Data 360: Addressing Salesforce CRM to Data 360 Data Mismatches - Permissions and Access Considerations

This article explains how access to activities is governed by these fields and the implications for private activities. When integrating Salesforce CRM with Data 360, data mismatches can occur if access permissions are not correctly set. Specifically, if a field in an object is related to another object, the user sending data from Salesforce CRM to Data 360 must have appropriate permissions for both objects.

Primary Cause:

Data mismatch issues between Salesforce CRM objects and Data 360 can arise because:

1. Permissions: Only the owner of an object or a user with sufficient permissions can view or edit it. Users without the necessary permissions, including API users who are not System Administrators, may not have access to private objects or fields, leading to discrepancies.
2. Activity Access: Access to Activities in Salesforce is determined by the access to their parent objects: WhoID and WhatID. To access an Activity, a user must have permissions for at least one of its parent objects. Activities that do not have any parent (WhoID or WhatID) are considered private, meaning only the owner has access. If the API user used for Data 360 integration is not a System Admin, it may not have access to these private activities, resulting in data mismatches.

Steps to Check if Fields Have Relationships on the Objects

1. 1. Access Object Manager:
      1. Log in to Salesforce.
      2. Navigate to the Object Manager tab in Setup.
   2. Identify the Affected Object:
      1. Use the search bar to locate the object experiencing the data mismatch.
      2. Click on the object to view its details.
   3. Review Fields and Relationships:
      1. Go to the Fields & Relationships section.
      2. Examine the list of fields to identify any that have a lookup or master-detail relationship to other objects.
   4. Verify Permissions:
      1. For each field with a relationship to another object, ensure that the user sending data from Salesforce CRM to Data 360 has the necessary access permissions to these related objects.
      2. Check both object-level permissions and field-level security settings.
   5. Check Activity Access:
      1. Review Activities to ensure that the Platform Integration user has access to the parent objects (WhoID and WhatID) of these Activities.
      2. Verify that Activities with no parent are not incorrectly flagged as private when they need to be accessed through the integration.