When you connect to Salesforce as the source application for a Celigo sync, the platform applies native awareness of your Salesforce account. It fetches a list of the objects in your Salesforce instance for you to select the objects and fields to sync.
In addition to – or instead of – the object selection, you can create or reuse any Salesforce export in your Celigo account to provide data to the sync. Note both the Objects and Exports tabs in Step 1: Source, below.
After choosing a source and establishing a connection, in this portion of the wizard you have a single source-level setting to configure: the schema drift policy, which instructs the sync how to handle changes in the source or destination structure automatically. Click Schema drift policy to review and modify the default settings. Note that this policy applies to any object or export in this source, unless you override it with a policy at the object/export level.
Next, select the source objects and exports to sync. In most cases, objects will be easier to work with; however, if the object list doesn’t provide sufficient coverage or you need customization, then rely on exports for greater flexibility. (Also see Extract sync source data from objects vs. exports.)
-
In the Objects tab, check the box to the left of the object, or check the box in the header row to select all objects.
-
Click in the Schema drift policy column to add an object-level schema drift policy if you want to override the source application’s policy.
-
-
Click the object name to expose its options.
-
Configure its modes:
-
Extract mode: Decide if you want to send the entire object and selected fields with each sync or only those values that have changed since the last sync.
-
All: Always extract complete data for this object and its selected fields, along with any selected child fields.
-
Delta: Extract only data that has changed since the previous sync run. Note that this setting is ignored if you are backdating the schedule to get complete data in a Historical sync.
-
-
Ingestion mode: Choose the way in which extracted data will be saved to the destination table:
-
Replace: Delete any data already in the destination table, and replace it with new data from the selected Salesforce object.
-
Append: Preserve all existing data in the destination table while adding new data from the selected object, even if a duplicate record would be added.
-
Merge: Add new records and replace any duplicate records in the destination table with the export data. All other records in the destination table will be preserved.
Important
When merging tables, you must set at least one primary key on each source object.
In addition, if you are setting the schema structure to normalize a child object (Preserve the array), then you must also assign a primary key within each normalized level of the array to apply to its resulting separate table at the destination. However, if the child object is flattened, you can assign a primary key at any level of the object’s hierarchy.
-
-
-
Choose the fields that you want to include with each sync, or check the box in the header row to select all fields in this object.
-
Configure the field-level settings, such as the primary key and mask. Notice that the sync retrieves the Salesforce metadata to provide Data type values and identify any
calculatedfields, which aren’t editable inline.
-
Then, click Next to save your settings and continue with Step 2: Destination, to choose how you want to have this data ingested at NetSuite Analytics Warehouse (NSAW) or Snowflake.
Click the Exports tab to see all of the Salesforce exports that you have access to in your account. Select the exports as you would for any other application you’ve chosen as the sync source.
The field listing for an object or export has the following columns that display information and allow you to configure how the field (or subfield) is synced, where applicable.
-
Primary key: Click
in a field’s entry to set it as a primary key in the destination table, or mark additional fields for a composite primary key.
-
Data type: Read-only, as found in your Salesforce account – for objects, based on Salesforce metadata, and for exports, based on the schema inferred.
-
Schema structure: For subfields, select whether you want to preserve the parent-child structure as shown or flatten the child records into individual rows alongside parent data.
-
Mask: Click
in a field’s entry to prevent sending sensitive values, such as personally identifiable information (PII), to the destination.
When you’ve completed defining the source application and data, click Next to save your settings and proceed to Step 2: Destination.
Choose from NetSuite Analytics Warehouse (NSAW) or Snowflake, unless you’re creating a sync in an integration that already targets one of those destinations, in which case it’s chosen for you.