Understand What Happens When You Enable Data Sync and Connections

Your Existing Dataflows Are Validated

Because data sync is based on your existing dataflows, CRM Analytics validates your scheduled dataflows to ensure that they are error free. Although dataflows with errors are not considered for data sync, CRM Analytics alerts you to any errors in sfdcDigest nodes when you enable data sync.

We recomment that before you enable Data Sync, review your scheduled dataflows for errors. In particular, look for incorrect object or field names in sfdcDigest nodes. If you see errors displayed when you enable Data Sync, fix them in your dataflows before you continue. When you fix errors in a dataflow, CRM Analytics considers it for a sync when you save the dataflow or upload the definition file.

CRM Analytics doesn’t consider unscheduled dataflows when you enable Data Sync. Make sure that any dataflow that you want to be considered is scheduled. See Schedule a Dataflow to Run Automatically.

All Fields in Multiple sfdcDigest Nodes for an Object Are Included in Data Sync

If your dataflows have multiple sfdcDigest nodes for the same object, each with a different set of fields, a superset of all these fields is included in data sync. In addition, if the same field has different attributes, such as type or isMultivalue, the attributes from the most recently created dataflow are used for data sync. Consider the following example dataflows, each containing an sfdcDigest node for the Opportunity object:

{    
   "Extract_OpportunitiesA": {        
      "action": "sfdcDigest",        
      "parameters": {            
         "object": "Opportunity",
         "fields": [                
            { "name": "Id"},
            { "name": "Name" },
            { "name": "StageName" },
            { "name": "CloseDate", "fiscalMonthOffset": 9 },
            { "name": "AccountId" },
            { "name": "OwnerId" }         
         ]  
      }    
   }

{    
   "Extract_OpportunitiesA": {        
      "action": "sfdcDigest",        
      "parameters": {            
         "object": "Opportunity",
         "fields": [                
            { "name": "Id"},
            { "name": "Name" },
            { "name": "StageName" },
            { "name": "CloseDate", "fiscalMonthOffset": 3 }
         ]  
      }    
   }

In the resulting data sync settings for this object, the Id, Name, StageName, CloseDate, AccountId, and OwnerId are included. The fiscalMonthOffset attribute for CloseDate is set to 3 from the most recently created dataflow.

We recommend that you review the fields in the sfdcDigest nodes of your dataflows. If the resulting data sync settings include fields that you don’t require, you can disable them in the settings for that object. If you have field attribute conflicts, ensure that the attributes you want to use for data sync are in the most recently created dataflow.

Advanced Filters on sfdcDigest Nodes Are Included in Data Sync

If an sfdcDigest node includes a complexFilterConditions parameter to apply an advanced filter, CRM Analytics adds this filter to the data sync settings for that object. When there are multiple sfdcDigest nodes with complex filters for the same object, only the filter from the most recently created or updated dataflow is added to the data sync settings. CRM Analytics ignores structured filters applied through filterConditions parameters.

We recommend that after you enable Data Sync, review each object’s data sync settings to verify that filters have been applied correctly. To use multiple filters for an object, we recommend that you remove any filter from data sync settings, and add the filters to the corresponding dataflow using the filter transformation (see filter Transformation).