Which statement is true about referencing standard Salesforce fields in OmniScript Data JSON?

Which statement is true about referencing standard Salesforce fields in OmniScript Data JSON?

• A. The syntax uses percent signs, e.g., %Account.Type%.
• B. The syntax uses curly braces, e.g., {Account.Type}.
• C. References are not supported.
• D. Fields must be in all caps.

Answer: (A)

OmniScript uses data-binding syntax wrapped in percent signs to pull values from the Data JSON at runtime. The example %Account.Type% tells OmniScript to resolve the Type field on the Account object from the current data context. This pattern is how you reference standard Salesforce fields in OmniScript; it works for fields surfaced by API responses or data sources, and you can point to nested or related data paths as they exist in the Data JSON. Curly braces would not be interpreted as bindings, and so {Account.Type} would be treated as literal text. References are indeed supported in OmniScript, and you don’t have to use all-caps names—the field name should match how it appears in Salesforce. This makes the percent-sign binding the correct and expected approach.

OmniScript uses data-binding syntax wrapped in percent signs to pull values from the Data JSON at runtime. The example %Account.Type% tells OmniScript to resolve the Type field on the Account object from the current data context. This pattern is how you reference standard Salesforce fields in OmniScript; it works for fields surfaced by API responses or data sources, and you can point to nested or related data paths as they exist in the Data JSON. Curly braces would not be interpreted as bindings, and so {Account.Type} would be treated as literal text. References are indeed supported in OmniScript, and you don’t have to use all-caps names—the field name should match how it appears in Salesforce. This makes the percent-sign binding the correct and expected approach.