Flexcard design standards, styling and reuse
The Flexcard best practices a consultant sets as standards: naming, avoiding trivial child cards, grouping conditions in Blocks, placeholders, reusable custom styles and branding, one multilingual card instead of copies, version hygiene, data pack export limits and Design Assistant warnings.
Discuss best practices for Flexcards.
~6 min read · 8 practice questions ·
What the exam expects
- Recommend Flexcard naming standards and readable designs with meaningful Output placeholders.
- Recommend fewer embedded components: no single-text child cards, similar conditions grouped in Blocks, rarely used data in collapsible Blocks or flyouts.
- Recommend the right styling reuse: Style tab, saved custom styles, conditional styles or a custom SLDS static resource, and avoid fragile custom CSS.
- Recommend one multilingual card with custom labels, removing unused versions, and the difference between versioning and cloning.
- Recommend fixes for data pack export limits and act on Design Assistant recommended limits.
Key terms: custom style (Style tab settings saved with Save As for reuse), multi-language support (the setting that lets {Label} merge fields translate text), version (a new iteration of the same card; one is active), data pack (an export of Flexcards and their dependencies), Design Assistant (real-time design feedback against recommended limits).
Key facts
- Detail
- Alphanumeric and single underscores; no spaces or dashes; letters and numbers only once Omnistudio Metadata API support is on
- Detail
- prefixObjectDetail in camel, pascal or snake case
- Detail
- Avoid; consolidate and use states or conditions
- Detail
- Group in Blocks for performance and maintenance
- Detail
- Style tab, Custom Style, Save As
- Detail
- Don't target DOM elements in components you don't own
- Detail
- {Label} merge fields with multi-language support; not cached
- Detail
- One at a time; activating replaces it wherever used
- Detail
- Unselect dependencies; no more than 10 elements per pack
- Detail
- 7 child Flexcards; 750 Data Table rows; 10 versions
Sources for this section (7)
- Test and Activate Flexcardstrailhead.salesforce.com (opens in a new tab)
- Omnistudio Naming Conventionshelp.salesforce.com (opens in a new tab)
- Style a Flexcardhelp.salesforce.com (opens in a new tab)
- Configure Flexcard Settingshelp.salesforce.com (opens in a new tab)
- Add States and Conditionstrailhead.salesforce.com (opens in a new tab)
- Omnistudio Flexcardshelp.salesforce.com (opens in a new tab)
- Recommended Limitshelp.salesforce.com (opens in a new tab)
- Why should a team avoid keeping a single-language and a multilingual version of the same Standard Runtime card?
- When should a consultant recommend a custom SLDS static resource over Style tab settings?
- When should you clone a Flexcard instead of creating a new version?
- What two changes fix a Flexcard data pack export that hits heap limits?
- What is the Design Assistant's recommended maximum of child Flexcards within a parent?
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 (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams