Troubleshooting and Debugging15% of the exam
Troubleshooting activation, publishing and deployment failures
How to read and fix activation, publishing and deployment failures: missing custom LWCs in a target org, Flexcards missing from Experience Builder, the lwr attribute behind LWR3008, Managed Package designer and Preview problems, and errors after enabling Omnistudio Metadata or Data Mapper Versioning.
Resolve publishing and deployment issues.
~6 min read · 6 practice questions ·
What the exam expects
- Resolve an activation failure in a target org caused by a missing custom LWC dependency.
- Fix a Flexcard that can't be dragged onto, or configured in, an Experience Builder page by choosing Publish Options targets.
- Fix an embedded Omniscript that fails with LWR3008 on an LWR site.
- Resolve Managed Package Runtime designer problems: Preview failing on Tooling API calls, and a record page opening instead of the Flexcard Designer.
- Diagnose errors after enabling Omnistudio Metadata or Data Mapper Versioning.
Key terms:
- Target org: the org components are deployed into, where every dependency must already exist.
- Publish Options: Flexcard targets that decide where the card can be placed.
- lwr attribute: attribute on lightning-omnistudio-omniscript needed when the card runs on an LWR site.
- Omnistudio Metadata: setting that enables Metadata API deployment and registers components in configuration tables.
Key facts
"No MODULE named markup://c:..."
- Detail
- Deploy every missing custom LWC to the target org, then activate again
Community Page target
- Detail
- Drag-and-drop component in Experience Builder
Community Default target
- Detail
- Editable properties when selected in Experience Builder
No target selected on save
- Detail
- App Page, Home Page and Record Page enabled as defaults
LWR3008
- Detail
- Missing lwr attribute on lightning-omnistudio-omniscript
Preview fails, Tooling API errors (Managed Package)
- Detail
- Add lightning.force.com and vf.force.com URLs to Remote Site Settings
Record page instead of designer (Managed Package)
- Detail
- Vlocity Card default record page set to Vlocity Card Designer
Error after enabling Omnistudio Metadata
- Detail
- Check names, Data Mapper version numbers, configuration tables
Referenced Data Mapper without active version
- Detail
- "No active version" error
Sources for this section (5)
- Activation and Access FAQhelp.salesforce.com (opens in a new tab)
- Activate and Publish a Flexcardhelp.salesforce.com (opens in a new tab)
- Flexcards Troubleshootinghelp.salesforce.com (opens in a new tab)
- Omnistudio Settingshelp.salesforce.com (opens in a new tab)
- Data Mapper Versioninghelp.salesforce.com (opens in a new tab)
- Why does activation in a target org fail with "No MODULE named markup://c:..."?
- When does an embedded Omniscript fail with LWR3008?
- Which target lets site admins edit a Flexcard's properties in Experience Builder?
- Which object's default Lightning record page must be Vlocity Card Designer for the Managed Package Runtime designer to open from the home tab?
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