To provide data to a sync, you can create or reuse any export from any third-party application in your Celigo account.
Tip
If object-level selection is supported for your endpoint, objects will prove much easier to work with in most cases. However, if the object list doesn’t provide sufficient coverage or you need customization, then rely on exports for greater flexibility.
Choose from any prebuilt/branded, database, or universal application that you can connect to, in the cloud or on premise.
Then, the Connect to source list is populated with connections in this account, to which you have permission, corresponding to the source application you chose. Select a connection, or click Create connection to make a new one.
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 every export in this source, unless you override it with a policy at the export or field level.
The wizard previews the exports from the selected application, available to you in your account. Each export’s results are represented as a single table for data ingestion.
Note
Webhooks and AS2 exports are not supported as sync sources and will not appear in the list.
-
Check the box to the left of the export, or check the box in the header row to select all exports.
-
Click in the Schema drift policy column to add an export-level schema drift policy if you want to override the source application’s policy.
-
-
Click the export name to expose its options.
-
Configure the settings for this table:
-
If necessary, click
to modify the export’s configuration. (Export settings do not offer an Extract mode; you can instead edit the export and select an option such as All or Delta in its Export type setting.)
-
Destination table name: Enter the name of the destination application table that will store the exported data. A default name, derived from the export name, is provided.
-
Ingestion mode: Choose the way in which exported data will be saved to the destination table:
-
Replace: Delete any data already in the destination table, and replace it with new data from this export.
-
Append: Preserve all existing data in the destination table while adding new data from the selected export, even if a duplicate record would be added.
Important
When merging tables, you must set at least one primary key on each source export.
In addition, if you are setting the schema structure to normalize a child array in the export (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 export is flattened, you can assign a primary key at any level of the export’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 export.
-
Choose the subfields that you want to include with each selected field. (A subfield represent a nested hierarchy in the exported JSON.)
-
Configure the field-level settings, such as the primary key and mask.
-
The field listing for an 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, inferred from the preview data.
-
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.