BigQuery To Salesforce: How Does It Work?

Before we get started, let’s first identify what BigQuery and Salesforce are. Google BigQuery is a cloud-based big data analytics web service for processing huge read-only data sets.

Salesforce is an online solution for CRM (customer relationship management) or CRM, able to give all your business departments such as sales, marketing, commerce, and customer service a collective shared view of your customers with one integrated CRM platform.

Now that we have that out of the way, imagine being able to empower your business by integrating these services together? Using a syncing platform such as Hightouch, you will be able to establish and upgrade standard or custom objects and also update custom picklist field values on those objects.

During the connection of your SalesForce destination with the Salesforce Authenticator setup as your two-factor authentication (2FA,) you may need to allow the request from your designated device, after which you return to the destination setup page and press ‘finish.’

Here is how you can bring over BigQuery to Salesforce for the effective results that you desire to keep your company running smoothly.

1. Insert Sync Mode

The Salesforce sync types that the Salesforce destination supports are “Object” and “Metadata” (Custom Picklists). The insert mode is one of the easiest modes for pushing data to Salesforce; it sends over new objects to Salesforce without updating the objects as they change in your warehouse.

The two different configuration parameters in Insert Mode are:

Hightouch To Salesforce Field Mappings: A collection of columns that will be sent over to new objects in Salesforce.

Salesforce Object Name: The title of the object (Account, Contact, etc.) that will be sent over to Salesforce.

2. Upsert Mode

Upsert mode differs from insert mode in that upsert sync mode delivers new objects to Salesforce and updates fields that change in your warehouse. With upset mode, new objects will be inserted into Salesforce, and all designated columns will remain current within Salesforce.

Upsert has three configuration parameters:

1. Salesforce Object Name: This is the name of the object (Account, Contact, or others) that will be updated inside Salesforce.

2. Hightouch to Salesforce External Unique Identifier Column Mapping: This is the name of the column on the Hightouch query as well as the name of an external ID for the object in Salesforce.

3. Hightouch to Salesforce Field Mappings: This is a list of columns that will be sent to new objects in Salesforce. Every time a sync occurs in Hightouch, these columns will get updated.

3. Update Mode

Update mode updates certain fields and columns on existing objects in Salesforce. Keep in mind that this mode doesn’t make brand new rows for an object within Salesforce. Instead, it updates columns on existing objects and also requires you to have access to the IDs of the objects you want to update within your warehouse.

Use Update mode when you happen to have objects in Salesforce that you want to add additional information or columns to. You can also use Update mode for continuously syncing data from your warehouse and also adding this data to existing objects within Salesforce, as well as the added benefit of having access to Salesforce object IDs within your warehouse.

Update has three configuration parameters:

Salesforce Object Name: This is the name of the object (Account, Contact, or others) that will be updated in Salesforce.

Hightouch ID Column: This is the name of the column of the Hightouch query that has a Salesforce object ID.

Hightouch to Salesforce Field Mappings: This is a list of columns that will be updated for objects in Salesforce. Each time a sync occurs in Hightouch, these columns get updated.

4. Multi-Object Syncing

This is for use connecting BigQuery to Salesforce, Hightouch supports syncing to several target objects and checks to see if your external ID mapping maps to either object to update the appropriate object.

5. Sync Modes And Configuration

Sync Modes: This particular integration is only able to support the All sync mode, and all active picklist values get swapped out every time a sync occurs.

Sync Configuration: Picklists are filtered by the object that they’re associated with, but when you are using Hightouch as your go-between for BigQuery and Salesforce, Hightouch lets you identify the picklist whose values you want to update.

6. Record Mapping And Field Mappings

Finally, keep in mind that custom picklist values contain two main fields, “label” and “API Name” (or value name). Both of these values must be unique amongst active values, though API Names must be distinctive across both inactive and active values within a particular picklist.

Records are able to be matched from your source to your Salesforce workspace by the API Name mapping of your choice. It is possible to sync custom labels from your source to your custom picklist values in Salesforce. In terms of limits, custom picklists can only contain a total of 1000 values per picklist, whether active or inactive.