Troubleshooting and Debugging15% of the exam
Troubleshooting Omniscript validation and rendering errors
How to diagnose Omniscript validation that fires too late, custom error messages that never replace the original, conditional views that never match, repeat limits, toasts that vanish, and screens that behave differently in Preview than on the page.
Resolve Omniscripts errors or UI not rendering correctly.
~6 min read · 7 practice questions ·
What the exam expects
- Make validation run while the user types instead of on blur.
- Write the Path and Value that let a Custom Error Message replace a Remote Action error.
- Fix a conditional view that never matches, including Date operands and hidden elements set to null.
- Set Limit Repeat for a maximum number of instances, and pick the Toast Mode that keeps a message visible.
- Separate documented Preview and element behaviour (mobile columns, Pattern, Mask) from real defects, and explain why a context ID that works in Preview fails on a page.
Key terms: onBlur (validation when the user leaves a field), commitOnChange (Setup JSON property that validates as the user types), Custom Error Message (Path, Value and Message that replace an error), right operand (the value a conditional view compares with), Toast Mode (how long a toast persists).
Key facts
Default validation
- Detail
- Runs on blur (onBlur function)
Validate while typing
- Detail
- Setup Edit as JSON: "commitOnChange": true; LWC delay half a second
Custom Error Message Value
- Detail
- Must match the original error exactly, including spaces
Nested error path
- Detail
- errors|0:errorMessage
Date right operand
- Detail
- ISO format, such as 2014-10-01T07:00:00.000Z
Hidden element
- Detail
- Its contents are set to null in the data JSON
Limit Repeat
- Detail
- 1 allows a maximum of two repetitions
Toast Mode
- Detail
- Sticky until closed; Pester three seconds; Dismissable three seconds or until closed
Context ID from Set Values
- Detail
- Works only in preview
"Inactive or not deployed" (Preview page)
- Detail
- Omniscript LWC can't exceed 4 MB
Similar error (Activation FAQ)
- Detail
- Insufficient object, field or record access, or missing Omnistudio object permissions
Sources for this section (6)
- Display Messageshelp.salesforce.com (opens in a new tab)
- Error Messageshelp.salesforce.com (opens in a new tab)
- Conditional Viewhelp.salesforce.com (opens in a new tab)
- Element propertieshelp.salesforce.com (opens in a new tab)
- Previewhelp.salesforce.com (opens in a new tab)
- Activation FAQhelp.salesforce.com (opens in a new tab)
- Why does an Omniscript show a validation message only after the user leaves the field?
- When does a Custom Error Message replace the original error?
- Why can a hidden Text element still trip a later validation check?
- Which Toast Mode keeps a toast visible until the user closes it?
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 (7 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams