Flexcards18% of the exam
Flexcard layout elements for role-based information
Which Flexcard element fits each display or input need (Field, Block, Data Table, Chart, Menu, Date, Toggle), how child Flexcards combine several data sources on one card, why Repeat Records multiplies charts and tables, and how custom permissions and User context variables tailor a card to the viewer.
Guide in designing Flexcards to display relevant information from multiple data sources using existing or available elements (inputs, menu, data tables, charts, etc.) ensuring the data is presented clearly and logically based on the user's role and context.
~7 min read · 9 practice questions ·
What the exam expects
- Recommend the display element for each need: Field and Block for a header, Data Table for sortable paged lists, Chart for summaries, Menu for many actions, Text for static text with merge fields.
- Recommend input elements such as Date, Toggle or Typeahead when users must enter or choose values on the card.
- Combine several data sources on one card with child Flexcards and attributes.
- Explain why a chart or table repeats and which setup option prevents it.
- Tailor a card to the viewer with custom permissions and User context variables such as userAccountId.
Key terms: display element (shows data or runs actions), input element (captures a value into the card's data JSON), child Flexcard (a card embedded in another card), Repeat Records (one card container per record), User context variable (properties of the logged-in user, such as {User.userAccountId}).
Key facts
Field element
- Detail
- Displays data source fields; doesn't accept entry
Input elements
- Detail
- Update the card's data JSON and can trigger actions
Data Table paging
- Detail
- Page Size and Page Limit add numbered page links; no page size shows all records
Clickable table field
- Detail
- Not supported; use row selection plus an event listener with {action.result.X}
Chart colors
- Detail
- More than six values repeat the palette colors
Repeat Records
- Detail
- True by default; deselect for tables, charts and children with own sources
Multiple data sources
- Detail
- Embed child Flexcards with their own data sources
Parent attribute
- Detail
- Child reads it as {Parent.attributeName}
Card custom permissions
- Detail
- Comma-separated; blank means everyone; visibility only
{User.userAccountId}
- Detail
- Id from the logged-in user's Account lookup
Sources for this section (8)
- Get Started with Flexcard Designertrailhead.salesforce.com (opens in a new tab)
- Show Data in a Tablehelp.salesforce.com (opens in a new tab)
- Add a Chart to a Flexcardhelp.salesforce.com (opens in a new tab)
- Test and Activate Flexcardstrailhead.salesforce.com (opens in a new tab)
- Configure Flexcard Settingshelp.salesforce.com (opens in a new tab)
- Explore Key Flexcard Featurestrailhead.salesforce.com (opens in a new tab)
- Embed Flexcard in a Flexcardhelp.salesforce.com (opens in a new tab)
- Flexcards Context Variableshelp.salesforce.com (opens in a new tab)
- Why should Repeat Records be off for a card whose Data Table lists all of an account's cases on Standard Runtime?
- When should a consultant recommend a child Flexcard with its own data source?
- When a Standard Runtime Data Table has Page Size set but fewer pages than Page Limit, what appears?
- When would a consultant read a value with {Params.fieldName} instead of {recordId}?
- What does leaving the card's custom permissions blank mean?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams