Omnata Product Documentation
  • Omnata Sync for Snowflake
    • What is Omnata Sync for Snowflake?
    • How it works
      • Terminology
      • Branching Mode
      • Sync Directions and Strategies
        • Outbound
        • Inbound
      • Rate Limiting
      • Access Control
      • Notifications
      • Security and Privacy
      • Internal tables
      • Internal Stored Procedures
      • FAQ
    • Step-by-step guides
      • 1. Install the Omnata Sync Engine
      • 2. Install the Omnata Plugin
      • 3. Configure the Plugin
      • 4. Create a connection
      • 5. Create a sync
    • Apps
      • Aerobotics
        • 📘Release History
      • Airtable
        • 📘Release History
      • Amazon Ads
        • Privacy Notice
      • ApprovalMax
        • 📘Release History
      • Bamboo HR
        • 📘Release History
      • Clockify
        • 📘Release History
      • Contentful
        • 📘Release History
      • GitHub
        • 📘Release History
      • Github
      • Google Ads
        • 📘Release History
      • Google Sheets
        • 📘Release History
      • HubSpot
        • 📘Release History
      • Hubspot
      • Infor Data Lake
        • 📘Release History
      • Jira
        • 📘Release History
      • LinkedIn Ads
        • 📘Release History
      • Mailgun
        • 📘Release History
      • Marketo
        • 📘Release History
      • Meta Marketing
        • 📘Release History
      • Microsoft Ads
        • 📘Release History
      • Microsoft Dynamics 365 Business Central
        • 📘Release History
        • 📘Release History
        • 📘Release History
        • 📘Release History
        • 📘Release History
      • Microsoft Entra ID
        • 📘Release History
        • 📘Release History
        • 📘Release History
        • 📘Release History
      • Microsoft Excel
      • Microsoft SQL Server
        • 📘Release History
      • Monday.com
        • 📘Release History
      • MRPeasy
        • 📘Release History
      • PayHero
        • 📘Release History
      • Pinterest Ads
        • Privacy Policy
      • PostgreSQL
        • 📘Release History
      • Salesforce
        • Salesforce Permissions needed
        • Formula Fields
        • How we use the Salesforce APIs
        • 📘Release History
      • Salesforce Marketing Cloud
        • OAuth for APIs, SFTP for file transfer with GPG on outbound
        • OAuth for APIs, SFTP for file transfer
        • OAuth for APIs, Cloud Storage for file transfer
        • 📘Release History
      • Shopify
        • Outbound sync data structures
        • 📘Release History
      • Slack
        • 📘Release History
      • Tiktok Ads
        • Privacy Policy
      • Typeform
        • 📘Release History
      • Wise
        • 📘Release History
      • Xero
        • 📘Release History
      • Zendesk Support
        • 📘Release History
        • 📘Release History
    • Plugins
      • Anatomy of a Plugin
      • Example Plugins
        • Example Plugin: Slack
        • Example Plugin: Zoho CRM
      • Creating Plugins
      • Advanced Plugin topics
        • Advanced rate limiting / concurrency
        • Custom Jinja filters
        • Custom Record Transformers
        • Dynamic Configuration Forms
        • Test case generation
    • Branching
      • Inbound Sync branching
      • Outbound Sync branching
    • Integrations
      • dbt
        • Validation Tests (coming soon)
    • 📘Release History
  • Omnata Connect for Salesforce
    • Overview
    • Getting Started
      • Install the Salesforce App
      • Connect to your data warehouse
        • Snowflake
        • BigQuery
        • Rockset
        • Firebolt
        • SingleStore (previously MemSQL)
      • Deciding which mode to use
    • Omnata with Salesforce Connect (External Objects)
      • Object Configuration
      • View your data in a list
      • Link to other objects
      • Use in a Report
      • Database schema changes
      • Writing to External Objects
    • Omnata with Salesforce Lightning Components
      • Object Configuration
      • View your data in a list
      • Link to other objects
      • Using the Lightning Component on a page
      • Assigning Permissions
    • Advanced Features
      • Row Level Filtering
      • Multi-Currency handling
        • About Multi-Currency
        • Support in Omnata Connect
        • Apex Features
    • Integrations
      • Datadog
    • Omnata with Salesforce Apex
    • Security
    • Use cases
      • Linked object drill-downs
      • Global Search
      • ERP and historical data
      • Embedded product metrics
    • Best Practices
      • Global Search
      • Change Management
      • Snowflake table design
      • Salesforce page layout
      • Salesforce Caching
Powered by GitBook
On this page
  • Child of Salesforce Object
  • Child of another External Object
  • Parent of Salesforce Object
  1. Omnata Connect for Salesforce
  2. Omnata with Salesforce Connect (External Objects)

Link to other objects

PreviousView your data in a listNextUse in a Report

Last updated 3 years ago

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

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:

TRANSACTION_ID (text, PK)
MERCHANT_ID (number(10,0))
TRANSACTION_DATETIME (datetime)
TRANSACTION_AMOUNT (number(10,2))

6b8a942c

123

2017-04-09 17:05:03.000

45.67

3c9a9e4d

123

2017-04-09 17:05:08.000

100.00

cec0b3c7

123

2017-04-09 17:05:12.000

21.00

42e8d696

123

2017-04-09 17:05:30.000

50.45

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.

here