The Short Answer
The Salesforce Certified Omnistudio Developer exam has 60 scored multiple-choice/multiple-select questions plus up to 5 unscored, a 105-minute time limit, a 72% passing score, a US$200 registration fee (US$100 to retake) and no prerequisite. Its questions align to the Spring '26 release (checked in October 2026 against the official exam guide).
This is the hands-on Omnistudio exam. You configure Flexcards, Omniscripts, Integration Procedures and Data Mappers, read the JSON they pass around, and fix them when they break: Troubleshooting and Debugging is a section of its own at 15%. The 72% bar is high, so a vague grasp of a property won't be enough.
Exam Details at a Glance
| Detail | Omnistudio Developer |
|---|---|
| Questions | 60 scored multiple-choice/multiple-select, plus up to 5 unscored |
| Time limit | 105 minutes |
| Passing score | 72% |
| Registration fee | US$200 (JPY 30,000), plus applicable taxes |
| Retake fee | US$100 (JPY 15,000), plus applicable taxes |
| Prerequisite | None |
| Release alignment | Spring '26 |
| Delivery | Proctored, online or at a testing center |
| References allowed | None |
| Maintenance | The certification's maintenance badge on Trailhead, once a year |
Source: the exam guide for every row, checked in October 2026. (The guide's "Purpose" paragraph calls it the "Omnistudio Developer Consultant Exam" once; it's a copy slip, and everything else on the page says Omnistudio Developer.)
72% of 60 is 43.2, so you need 44 correct answers and can miss only 16. You get about 1.6 minutes for each of up to 65 questions. Many stems include a JSON payload, a property list or an error message, so budget the extra time for reading those carefully rather than for re-reading the scenario. For fees and retake rules across every Salesforce exam, see Salesforce certification cost and retake fees.
Who the Exam Is For
The exam guide describes a candidate with one year of developer experience plus 3 to 6 months of design, implementation and deployment work with Omnistudio tools, typically a Salesforce Platform Developer, App Builder, Solution Architect, Technical Architect or UI Developer. They turn defined business requirements into declarative Omnistudio solutions with conditional navigation that read and write Salesforce and external data using JSON and REST.
The guide lists the skills it expects: the development lifecycle and its environments, out-of-the-box and customized builds, pre-configured elements from the Industry Process Library, creating test data, choosing declarative versus programmatic methods, and using Omnistudio's own debugging tools. It also expects familiarity with HTML, JavaScript and CSS as concepts.
The exclusions are specific. You aren't expected to do browser console log debugging, write Lightning Web Components, Apex or Angular, tune performance and scalability, integrate with other industry products, or install and configure the package. So the debugging questions are about Omnistudio's designer tools, not Chrome DevTools.
On names: Salesforce Help now says Data Mappers (formerly DataRaptors), Omniscripts and Flexcards. You'll still meet the old names in older modules and community answers.
The Six Exam Sections and What They Test
All weights and objectives come from the official outline.
| Section | Weight | About this many questions (of 60) |
|---|---|---|
| Omnistudio Fundamentals | 18% | 11 |
| Flexcards | 15% | 9 |
| Omniscripts | 20% | 12 |
| Integration Procedures | 15% | 9 |
| Data Mappers | 17% | 10 |
| Troubleshooting and Debugging | 15% | 9 |
Omnistudio Fundamentals (18%)
Use cases, requirements, the two runtimes and upgrades, licenses and permission sets, plus two objectives the Consultant exam doesn't have: the tools for an end-to-end implementation (Salesforce CLI, VBT, migration), and testing, versioning and cloning.
Learn deployment per runtime. On Managed Package Runtime, Salesforce's deployment and migration page says you move components between orgs with the Omnistudio Build Tool (formerly Vlocity Build Tool or VBT), a Node.js tool that packages DataPacks for source control, or with IDX Workbench, or by exporting and importing DataPacks. On Standard Runtime, Clean Metadata Deployment turns Omnistudio components into standard metadata you deploy with Salesforce CLI, change sets, Metadata API or packages. Its new types (OmniscriptDefinition, IntegrationProcdDefinition, DataMapperDefinition, FlexcardDefinition) need API version 67.0 or later, and the feature is available only on the standard runtime and designer. Moving from one runtime to the other is what the Omnistudio Migration Assistant, a Salesforce CLI plugin, automates, though converting Angular components and deploying custom LWCs stay manual.
Flexcards (15%)
Configuring data sources and testing the JSON they return, single and multi-level cards with layouts and repeaters, actions (launch an Omniscript, fire events, update other components), event listeners, session variables, public attributes, styling and themes, states for conditional rendering, and embedding across channels.
Watch for: field-level security on query data sources. The Flexcard data source page says the EnableQueryWithFLS Omni Interaction Configuration makes SOQL and SOSL sources show only the fields a user can see, and that Salesforce turned it on by default during the week of February 2, 2026. A card that "lost" fields for some users may be working as designed. The same page notes that the field picker only lists fields with non-null values on the test record, so pick a well-populated test record before mapping.
Omniscripts (20%)
The biggest section: building with Group, Action and Input elements, child Omniscripts, Flexcards and custom LWCs, styling, multi-language, save options, Knowledge Articles, the Messaging Framework, and embedding.
Watch for: the Messaging Framework on Standard Runtime. Salesforce's Omniscript-to-LWC page says the pubsub module doesn't operate when Standard Runtime is enabled, and points to window post messages or session storage messages instead. On the package runtime, an Action or Step passes data with merge syntax, for example a value of %accountId% to send the response node of that name.
Integration Procedures (15%)
Groups, Data Mapper actions, Remote Actions, HTTP Actions, Response Actions and sub-procedures, conditions, loops and branching, chainable procedures, caching, Try/Catch and the Response Action.
Three pages carry most of this section:
- Chaining. The long-running settings page says every action runs in one transaction by default, and that with chaining enabled a step that would exceed a governor limit continues in a separate transaction. You turn it on with the Chainable checkbox on the calling Omniscript action (or
chainable: truefrom REST), optionally add Queueable for an Async Apex job with higher limits, and can set Chain On Step on a specific step. One practical tip from that page: if a Data Mapper Post action is followed by an HTTP Action, set Chain On Step on the Data Mapper Post to avoid "You have uncommitted work pending". - Try/Catch. A Try-Catch Block runs its steps and catches a failure. Fail on Block Error fails the whole procedure, Failure Response returns a value (which can be a formula), and Custom Failure Response calls an Apex class and method.
- Caching. The caching page sets Org Cache at up to 48 hours for non-sensitive shared data and Session Cache at up to 8 hours for user-specific data. You can cache the whole response, cache only some steps with a Cache Block, or cache the definition (metadata), which Disable Definition Cache turns off.
The HTTP Action makes REST calls (GET, POST, PUT, PATCH or DELETE), takes a Named Credential for authentication, and offers a Retry Count and a timeout in milliseconds.
Data Mappers (17%)
Configuring all four types against sources and targets such as JSON, XML, custom Apex, sObjects, PDF and Docusign, formulas across types, and mapping input to output structures.
From the Data Mappers overview: an Extract reads one or more objects, a Turbo Extract reads one object plus related fields with no formulas, custom JSON, defaults or transformations, a Load writes from JSON, XML or custom input, and a Transform reshapes data in memory without querying Salesforce. The Turbo Extract configuration page adds the details that make good questions: an IN filter operator that matches against an array in the input, a LIMIT from 1 to 50,000 (default 50,000), parent relationships up to five levels, a cache time-to-live of at least 5 minutes, and a "Check field level security before execution" option that disables Org Cache. For example, with the filter LastName IN Names, this input returns every contact named Miller or Torres:
{ "Names": ["Miller", "Torres"] }
Troubleshooting and Debugging (15%)
Flexcard display and state issues, Omniscripts that error or don't render, wrong Data Mapper output, Integration Procedure errors, caching problems, permissions, missing or broken JSON, publishing and deployment failures, and the Debug Console.
Watch for: these documented causes, each a likely scenario:
- A cached result that won't update. Check whether the response is in Org or Session Cache, and test with the cache off. The caching page suggests running a procedure in Preview with Disable Definition Cache checked and then unchecked.
- A component that won't compile or appears blank after the move to Standard Runtime. The runtime switch page says Standard Runtime enforces stricter field-level security than the package runtime, so FLS must be set explicitly on Omni Process Compilation, Omni Data Transformation and Omniscript Saved Sessions; missing permissions cause LWC compilation errors and visibility issues.
- A Flexcard Preview that fails on a new org (Managed Package Runtime). The Flexcard troubleshooting page says Remote Site Settings must include the org's lightning.force.com and vf.force.com URLs, and that components which embed each other can loop until the browser's call stack overflows.
- An HTTP step you can't see into. Use the HTTP Action's Pre-Action and Post-Action logs, which write to the Preview tab's debug output.
- Apex tests that make real callouts. Salesforce's unit testing page says that in the core runtime HTTP mocking isn't possible when you test an Integration Procedure from Apex, so real HTTP calls happen.
How the Developer Exam Differs from the Consultant Exam
The two credentials cover the same four tools, but the verbs differ. Developer asks you to configure, implement and resolve, and adds deployment tools, chainable procedures, Try/Catch and a debugging section. The Consultant exam asks you to recommend and justify designs, and explicitly excludes configuration and troubleshooting. If you're deciding which to take first, or planning to hold both, our Omnistudio Consultant certification guide covers the design side.
A Six-to-Eight-Week Study Plan
- Read the exam guide and score yourself. Rate each of the 46 objectives from 1 to 3. Our guide to using the exam outline to plan your study shows how to weight the gaps.
- Take a baseline. Try the 18 free Omnistudio Developer practice questions to see how JSON and property questions are framed and find your weakest section.
- Work the official trail. The guide recommends the Prepare for your Salesforce Omnistudio Developer Certification trail (about 11.5 hours on Trailhead, with a step on troubleshooting and debugging), plus the instructor-led Build Guided Experiences with Omnistudio Tools (OMS435).
- Build one end-to-end flow. A Flexcard on Account that launches an Omniscript, which calls an Integration Procedure with a Data Mapper Extract, an HTTP Action inside a Try-Catch Block, and a Data Mapper Load. Then break it on purpose: a wrong JSON path, a missing field permission, a stale cache.
- Deploy it. Move the flow to a second org with the tool your runtime uses, and note what failed and why.
- Practice under time. Book the exam when you're steadily above 72%, and can say for each wrong option which property, path or runtime makes it wrong. Our guide to answering Salesforce scenario questions helps with multi-select questions.
Omnistudio Developer Practice Exam on Certifyforce
Certifyforce has a separate practice bank for this exam, written to the Developer outline and checked against Salesforce Help, the Salesforce Developers blog and Trailhead. It isn't affiliated with Salesforce, and it contains no recalled exam questions or brain dumps.
- The Omnistudio Developer practice exam: 300 reviewed questions across all six sections, including troubleshooting, with timed 60-question exams weighted like the real one, section practice, and an explanation and source for every answer. The full pack is launching soon.
- 18 free practice questions spread across the sections by weight, each with the answer, why the other options are wrong and the page it was checked against. No account needed.
Frequently Asked Questions
How many questions are on the Omnistudio Developer exam?
60 scored multiple-choice/multiple-select questions plus up to 5 unscored ones, in 105 minutes, with a 72% passing score, per the exam guide.
How much does the Omnistudio Developer exam cost?
US$200 (JPY 30,000) plus applicable taxes, and a retake costs US$100 (JPY 15,000), per the exam guide.
Is there a prerequisite?
No, but the guide describes a candidate with one year of developer experience and 3 to 6 months of hands-on Omnistudio work.
Do I need to write Apex or Lightning Web Components?
No. The guide says you aren't expected to have LWC, Apex or Angular development experience. You do need to know when a custom LWC or a Remote Action is the right element, and how it's configured inside an Omniscript or Integration Procedure.
Which deployment tools are tested?
The outline names Salesforce CLI, VBT and migration tools. Know which runtime each belongs to: the Omnistudio Build Tool and IDX Workbench for Managed Package Runtime, Salesforce CLI with Clean Metadata Deployment for Standard Runtime, and the Omnistudio Migration Assistant for moving between them.
How do I keep the certification?
Complete the Omnistudio Developer maintenance badge on Trailhead once a year. If you miss the due date, the certification expires.