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
  • Currency Selection Options
  • Get ISO currency code from another column
  • Use a fixed currency
  • Use the Organizations default currency
  • Advanced Multi Currency (Dated Exchange Rates)
  1. Omnata Connect for Salesforce
  2. Advanced Features
  3. Multi-Currency handling

Support in Omnata Connect

With Omnata Connect, a Number field can be configured to support Multi-Currency. In this mode:

  • The value in the original Number field is converted from the designated original source currency into the user's display currency.

  • A Text field is added to the External Object which displays the number in the source currency including the currency code, plus the user’s currency in parentheses if different. This field is used as a readable presentation of the currency, but not for sorting or filtering as it’s just a text field.

To achieve this, first we provide a method of designating a currency for each record for a numeric column in the data warehouse.

Currency Selection Options

Get ISO currency code from another column

Using this option, you can support single database tables that contain a variety of currencies.

For example:

ITEM_ID
PRICE
CURRENCY

1

100.00

USD

2

150.00

USD

3

2000.00

JPY

By nominating the CURRENCY column as the currency code source, the value in PRICE will be interpreted appropriately.

Note: For all currency code values present in the database table, there must be a currency code configured in Salesforce so that a rate can be applied.

Use a fixed currency

Using this option, you can choose from a static list of currencies available in the Organization.

Use the Organizations default currency

This option is similar to choosing a fixed currency, except it will automatically apply whatever is the default currency (the "corporate" rate).

Advanced Multi Currency (Dated Exchange Rates)

If Advanced Multi Currency is enabled in the Salesforce Organization, a date column from the database table can be nominated as the effective date of conversion.

For example:

ITEM_ID
PRICE
CURRENCY
SALE_DATE

1

100.00

USD

2018-01-05

2

150.00

USD

2018-06-08

3

2000.00

JPY

2019-05-03

By nominating SALE_DATE as the date column, the Omnata Connect adapter will look up the historical conversion rate for that currency at that point in time.

When using this option, it is important to keep your Salesforce Organization's currency rates table maintained.

PreviousAbout Multi-CurrencyNextApex Features

Last updated 3 years ago