Openflow Connector for Salesforce Bulk API: Salesforce formula fields¶

This topic describes how the Openflow Connector for Salesforce Bulk API translates Salesforce formula fields into Snowflake SQL views, including supported functions and limitations.

How formula views work¶

When Enable Views Creation is set to true, the connector performs the following for each object that has formula fields:

1. Retrieves the formula expressions from the Salesforce object metadata via the Describe API.
2. Parses each formula expression and translates it into equivalent Snowflake SQL.
3. Generates a CREATE OR REPLACE VIEW statement that combines non-formula columns from the base table with the translated formula expressions as computed columns.
4. Runs the DDL against Snowflake to create or update the view.

The resulting view is named <Object Type>_FORMULA_VW. For example, the Account object produces a view named ACCOUNT_FORMULA_VW. You can query this view to obtain formula field values alongside the replicated data.

The view is automatically updated whenever the connector detects schema changes in the source object, ensuring that formula definitions stay in sync with Salesforce.

Cross-object formula fields¶

Salesforce formulas can reference fields from related objects using relationship traversal (for example, Account.Owner.Name). The connector supports these cross-object references by generating LEFT JOIN clauses in the view definition. Each relationship traversal produces a join to the corresponding related table in Snowflake.

For cross-object formulas to work correctly, the related objects must also be replicated by the connector. If a related object is not being synced, the formula columns that reference it are replaced with a typed NULL in the view. The remaining formula columns continue to compute normally. The affected columns have a LOOKUP_NOT_SYNCED comment. Once the referenced objects are added to replication and synced, the view is automatically rebuilt on the next connector run.

Chained formula fields¶

Formula fields that reference other formula fields (chained formulas) are supported. The connector resolves the dependency graph before SQL generation and expands each referenced formula field’s expression into the referencing formula’s AST. Multi-hop chains are fully expanded. If a dependency cannot be translated, the dependent field also returns NULL and the column comment indicates FORMULA_CHAIN_NOT_SUPPORTED.

Formula view column comments¶

Each formula column in the generated view includes a SQL COMMENT annotation:

• For successfully translated formulas, the comment contains the original Salesforce formula expression.
• For formulas that could not be translated, the comment contains the failure reason code followed by the original Salesforce formula expression, separated by a colon (for example, FUNCTION_NOT_SUPPORTED: IMAGE(url, 'alt')).

You can inspect these comments by running DESCRIBE VIEW <view_name> in Snowflake.

Supported formula functions¶

The following Salesforce formula functions are translated into equivalent Snowflake SQL:

In addition to functions, the following operators are supported:

• Arithmetic: +, -, *, /, ^ (exponentiation, translated to POWER)
• Comparison: =, ==, !=, <>, <, <=, >, >=
• Logical: AND, OR, &&, ||
• String concatenation: & (translated to || with COALESCE null handling)
• Unary: - (negation), NOT

Unsupported formula constructs¶

The following formula constructs are not yet supported. Support for additional functions and constructs will be added in future releases. When a formula uses any of these, the corresponding column in the view returns NULL and the column comment indicates the failure reason.