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
  • Overview
  • Operators
  • = (equality)
  • includes
  • arrays_overlap
  • Boolean operators
  • Operands
  1. Omnata Connect for Salesforce
  2. Advanced Features

Row Level Filtering

PreviousAdvanced FeaturesNextMulti-Currency handling

Last updated 2 years ago

Overview

Each External Object can have a single row level filter applied, which restricts records to a subset that match some User attribute.

This will add an automatic WHERE clause to the database query, of the form

<column name> <operator> <salesforce operand>

This clause is automatically applied, regardless of any other filtering occurring on the object.

Row Level Filtering is configured in the Setup UI, under the "Omnata Connect" tab.

Operators

The following operators are supported:

= (equality)

The value of the Salesforce operand must match the value in the database column. The data type of the Salesforce operand should be comparable to the data type in the database.

includes

The value of the Salesforce operand must appear in an Array column. This operator is only supported in Snowflake and Rockset, and can only be used with array columns.

arrays_overlap

The value of the Salesforce operand will be split into an array on the ';' character, and Multipicklist fields are a good choice as they are automatically delimited on this character. This operator is only supported in Snowflake and Rockset, and can only be used with array columns. The row will be visible if the two arrays share at least one value in common.

Boolean operators

AND: Both the Salesforce operand and the database column must be boolean. The following truth table determines whether or not the row will be visible:

Database
Salesforce
Row Visible

TRUE

TRUE

Yes

TRUE

FALSE

No

FALSE

TRUE

No

FALSE

FALSE

No

OR: Both the Salesforce operand and the database column must be boolean. The following truth table determines whether or not the row will be visible:

Database
Salesforce
Row Visible

TRUE

TRUE

Yes

TRUE

FALSE

Yes

FALSE

TRUE

Yes

FALSE

FALSE

No

XOR: Both the Salesforce operand and the database column must be boolean. The following truth table determines whether or not the row will be visible:

Database
Salesforce
Row Visible

TRUE

TRUE

No

TRUE

FALSE

Yes

FALSE

TRUE

Yes

FALSE

FALSE

No

NAND: Both the Salesforce operand and the database column must be boolean. The following truth table determines whether or not the row will be visible:

Database
Salesforce
Row Visible

TRUE

TRUE

No

TRUE

FALSE

Yes

FALSE

TRUE

Yes

FALSE

FALSE

Yes

NOR: Both the Salesforce operand and the database column must be boolean. The following truth table determines whether or not the row will be visible:

Database
Salesforce
Row Visible

TRUE

TRUE

No

TRUE

FALSE

No

FALSE

TRUE

No

FALSE

FALSE

Yes

Operands

The left hand side is always just the value in the specified database column.

The right hand side is evaluated in Salesforce per query, in the context of the user. It can be:

  • User attribute: An attribute of the current User

  • User is member of Public Group (directly): A boolean value indicating whether or not the current user is a member of a Public Group. "Directly" means that the user must be directly assigned to the group, not another group which belongs to this group.

  • User not member of Public Group (directly): A boolean value indicating the inverse of the above; whether or not the current user is not a member of a Public Group.

  • User is assigned Permission Set: A boolean value indicating whether or not the current user has been assigned a particular Permission Set.

  • User not assigned Permission Set: A boolean value indicating indicating the inverse of the above; whether or not the current user has not been assigned a particular Permission Set.