Flexcards15% of the exam
Repeat records, child Flexcards and recursive layouts
How Repeat Records and the render key turn data source records into cards, when to deselect Repeat Records, and how child Flexcards receive parent data through Data Node, attributes and Is Recursive for multi-level layouts.
Construct single and multi-level Flexcards, organizing data using layouts, and repeaters.
~7 min read · 4 practice questions ·
What the exam expects
- Decide when Repeat Records stays selected and when to deselect it (Datatable, Chart, list, containers with their own data).
- Add a render key so only the updated repeated card is regenerated.
- Build a multi-level card: embed a child Flexcard and feed it with a Data Node or attributes.
- Configure Is Recursive for hierarchical JSON of any depth.
Key terms: Repeat Records (one card container per returned record), render key (the field that identifies a repeated card in the DOM), child Flexcard (a card embedded in another through the Flexcard element), Data Node (the parent's data passed to the child in place of its own source), Is Recursive (the child embeds itself at each level of a data node).
Key facts
Repeat Records
- Detail
- One card container per record instead of one card for all
Render key
- Detail
- Regenerates only the updated card record in the DOM
Managed Package rule
- Detail
- Deselect only for a Chart or Datatable; other elements need Repeat Records even for one record
Data Node set
- Detail
- Child data source ignored; parent changes re-render the child
Parent attribute
- Detail
- Read in the child as {Parent.attributeName}
Is Recursive
- Detail
- Repeats until the data node no longer exists or is empty
Recursive conditions
- Detail
- One false record condition hides its nested records
- Why does a render key make a repeated card list faster to update?
- When does a recursive child Flexcard stop nesting?
- Which Data Node passes only the second record to a child?
- Why might nested records vanish from a recursive card?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (4 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams