For a Field element in a FlexCard that should display the AccountName, which data reference syntax is correct?

Study for the OmniStudio Developer Test. Focus with flashcards and multiple-choice questions, each with hints and explanations. Get ready for your exam!

Multiple Choice

For a Field element in a FlexCard that should display the AccountName, which data reference syntax is correct?

Explanation:
In a FlexCard, dynamic values come from binding to the data context using data reference syntax: wrap the field name in curly braces. This tells the card to evaluate and render the actual value from the data payload rather than displaying literal text. Using {AccountName} binds to the AccountName field in the current data context, so the card will display the real account name at runtime. If you write the field name without braces, it would render as the literal text "AccountName" instead of the value. Referencing records with braces or using the word records alone would not pull the single field value you want (they refer to a collection or are treated as static text). In this scenario, the top-level field to display is AccountName, so {AccountName} is the correct binding.

In a FlexCard, dynamic values come from binding to the data context using data reference syntax: wrap the field name in curly braces. This tells the card to evaluate and render the actual value from the data payload rather than displaying literal text.

Using {AccountName} binds to the AccountName field in the current data context, so the card will display the real account name at runtime. If you write the field name without braces, it would render as the literal text "AccountName" instead of the value. Referencing records with braces or using the word records alone would not pull the single field value you want (they refer to a collection or are treated as static text). In this scenario, the top-level field to display is AccountName, so {AccountName} is the correct binding.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy