Troubleshooting and Debugging15% of the exam

Troubleshooting Flexcard display, actions and states

How to diagnose and fix common Flexcard failures: Data Table search and selectrow data, double-height charts, Data action responses that never reach the card, navigate and close actions in flyouts, autolaunched flow data sources and record change listeners on Experience Cloud pages.

Official exam objective
Resolve Flexcards display and state issues.

~8 min read · 6 practice questions ·

What the exam expects

  • Explain why a Data Table column can't be searched and why a selectrow listener sees only one row.
  • Fix a chart that renders at double height in a standard Flexcard component.
  • Read the action debugger to find why a Data action's response never reaches the card or a child card.
  • Keep navigate and close actions working inside modal and popover flyouts.
  • Diagnose an autolaunched flow data source that returns old output or rejects an input type.
  • Explain why a record change listener on an Experience Cloud page doesn't refresh after a backend update.

Key terms: Ignore Response (Data action option that skips updating the card's JSON), Response Node (where a Data action saves returned data), closemodal (the event name that closes a modal flyout), selectrow (the Data Table event for the currently selected row), record change listener (an event listener that reacts when a record on the card changes).

Key facts

Hidden column search
Detail
Is Visible off means the column can't be searched, even with Is Searchable on
selectrow payload
Detail
Only the currently selected row; previous selections need event handling
Double-height chart
Detail
Enable Lightning Web Security (beginning Summer '22)
Ignore Response
Detail
Skips the JSON update; debugger shows ignoreResponse true
Response Node
Detail
record for one object; alphanumeric name for several records
Navigate in a flyout
Detail
Add an Event action named closemodal
Autolaunched flow version
Detail
The card always runs the active version
Unsupported flow inputs
Detail
Picklist, Multi-Select Picklist, Apex-Defined
Experience Cloud record change
Detail
Fires only for same-tab edits, not backend processes
Sources for this section (6)
  • Why does a Data action's response appear in the action debugger but not in the card's JSON?
  • When should a Data action's Response Node be record?
  • Why can't a listener rebuild every selected Data Table row from one selectrow event?
  • Which three input variable types can't an autolaunched flow invoked from a Flexcard use?

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 (6 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Unlimited timed practice exams

Practice for the Omnistudio Developer exam