Link to other objects

You can link your External Objects to other existing Objects in a few different ways which are described in detail here.

Linking objects will enable CRM users to drill up and down between objects. For example, users will be able to drill-down from native Salesforce objects like Accounts and Contacts to External Objects from your data warehouse like Orders or Transactions.

Linking objects is achieved by converting Salesforce fields from their native type, to a Lookup field. Omnata Connect offers a simplified setup process:

Child of Salesforce Object

Within Salesforce, this type of lookup is known as Indirect, and is the most common use case with External Objects.

To use Indirect, you must first have a Salesforce Object (Standard or Custom) with a custom field that contains identifiers matching those in your Snowflake table. For example, if you had a Snowflake table named FINANCIAL_TRANSACTIONS:




2017-04-09 17:05:03.000




2017-04-09 17:05:08.000




2017-04-09 17:05:12.000




2017-04-09 17:05:30.000


You could link to a Merchant ID field on the Account Object, provided it had a compatible data type, and had the "unique" and "external" flags set:

Note: The custom field should also be marked as case sensitive, to ensure its values match with those in Snowflake.

Now that the objects are linked in this way, the external objects should automatically appear on the 'Related' tab of the parent object ('Account' in this example), provided there are matching records.

Child of another External Object

Within Salesforce, this type of lookup is known as External. It is similar to Indirect Lookup, except that the parent record also sits outside of Salesforce. This is useful when your Data Warehouse contains hierarchical data and you need to drill down.

Parent of Salesforce Object

This less-common pattern is used when multiple Salesforce Standard or Custom objects need to be linked to a single record in the Data Warehouse.

Last updated