Overview
Implement Microsoft Power Platform was weighted at 5–10% of MB-240. Field Service is a set of model-driven apps on Dataverse, so a functional consultant extends it with standard Power Platform tools rather than custom code. The first group covers model-driven app configuration: creating and configuring forms, views and app navigation.
The second group covers building task-specific canvas apps and custom pages, embedding them in Field Service, and using Power Automate cloud flows to automate tasks around work orders, bookings and assets. Typical examples include a canvas app for a quick site survey, a custom page that gives dispatchers a focused view, and a flow that notifies a supervisor when a high-priority work order is created or that updates a record when a booking completes.
How it's tested
Expect requirement-to-tool questions. The scenario states what users need, such as an extra column in a list, a simplified data entry screen, or an automatic action when a record changes, and the answer is the lightest Power Platform feature that meets it. Avoid choosing code or a full app when configuration will do.
-
Form or view change
Users need different columns, fields or sections, and you choose between editing a form, a view or the app's navigation.
-
Canvas app or custom page
A focused task screen is required, and you decide whether a canvas app or a custom page embedded in the model-driven app fits.
-
Automation trigger
Something must happen when a record is created or changes, and you choose a Power Automate cloud flow with the right trigger.
Dispatchers want an alert in Microsoft Teams whenever an emergency work order is created after hours. No new screen or table is needed, so canvas apps and form changes are unnecessary. An automated cloud flow using the Dataverse trigger for a new work order row, with a condition on priority and time, posts to the Teams channel. This meets the need with configuration only.
Functional groups 2
Official functional groups from the Microsoft outline, in outline order.
6.1 Configure model-driven appsForms, views and navigation.
- What it means
- This group covers configuring the model-driven apps Field Service is built on: creating and configuring forms, creating and configuring views, and configuring navigation in the app designer.
- What to understand
- Main forms define how a record looks, quick create forms speed up entry and quick view forms show related data inline. Views are system (public) or personal and control columns, sorting and filters in lists and lookups. Navigation is set in the app designer through the site map, where areas, groups and subareas expose tables and pages. Changes belong in a solution so they move cleanly between environments, and customizing Microsoft's own forms is safer through copies or added sections.
- How it shows up
- Look for a request to show more columns, change a form layout or add a table to the menu.
- Common confusion
- A view controls lists; a form controls a single record's layout.
6.2 Create custom apps and automationsCanvas apps, custom pages, embedding apps and Power Automate cloud flows.
- What it means
- This group covers building task-specific canvas apps and custom pages, embedding apps inside Field Service, and using Power Automate cloud flows to automate tasks and enhance Field Service processes.
- What to understand
- Canvas apps give pixel-level control and suit focused tasks or mobile screens. Custom pages are canvas-based pages that live inside a model-driven app and its navigation, which makes them the usual way to embed a focused screen in Field Service. Cloud flows can be automated (triggered by Dataverse row events), instant (started by a user) or scheduled. Typical Field Service flows send notifications, create follow-up records or synchronize with other systems.
- How it shows up
- Expect a choice between a custom page, a standalone canvas app and a flow for a stated need.
- Common confusion
- Custom pages sit inside the model-driven app; standalone canvas apps run separately.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Main form
Primary layout for a record.
- Remember
- Field Service forms are also used on mobile.
- Tested as
- Layout questions.
- Trap
- Editing a list when the form is the issue.
-
Quick create form
Short form for fast record entry.
- Remember
- Opens without leaving the current screen.
- Tested as
- Data entry questions.
- Trap
- Expecting it on every table automatically.
-
Quick view form
Read-only related data on another form.
- Remember
- Shows lookup record details inline.
- Tested as
- Related data scenarios.
- Trap
- Trying to edit through it.
-
System view
Shared list definition for all users.
- Remember
- Controls columns, filters and sorting.
- Tested as
- List and lookup questions.
- Trap
- Changing a personal view for everyone.
-
App designer navigation
Site map of areas, groups and subareas.
- Remember
- Exposes tables, dashboards and pages.
- Tested as
- Menu questions.
- Trap
- Assuming a table appears once created.
-
Canvas app
Freely designed app for a focused task.
- Remember
- Can be embedded or run standalone.
- Tested as
- Custom screen scenarios.
- Trap
- Building one for a simple form change.
-
Custom page
Canvas-based page inside a model-driven app.
- Remember
- Preferred way to embed focused screens.
- Tested as
- Embedding questions.
- Trap
- Confusing it with a web resource.
-
Automated cloud flow
Flow triggered by a data event.
- Remember
- Dataverse row added, modified or deleted triggers.
- Tested as
- Automation scenarios.
- Trap
- Using a scheduled flow for real-time needs.
-
Instant cloud flow
Flow started by a user action.
- Remember
- Can be run from a button or command.
- Tested as
- On-demand automation.
- Trap
- Expecting it to run on record changes.
-
Solutions
Containers for customizations.
- Remember
- Move forms, views, apps and flows between environments.
- Tested as
- ALM questions.
- Trap
- Customizing directly in production without a solution.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Form vs. view vs. navigation
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Form | Layout of one record | Controls fields and sections shown | Changing it to alter list columns |
| View | Definition of a list of records | Controls columns, filters and sorting | Expecting it to change record layout |
| Navigation | App menu structure | Controls what users can reach | Thinking new tables appear automatically |
Canvas app vs. custom page vs. cloud flow
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Canvas app | Standalone focused app | Runs on its own or embedded | Using it when a form change is enough |
| Custom page | Canvas page inside a model-driven app | Shares app navigation and context | Building a separate app instead |
| Cloud flow | Automation without a screen | Runs on triggers, schedules or user action | Using it to build a user interface |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Canvas app for a layout tweak
- What candidates pick
- Build a canvas app to show three extra fields.
- Why it looks right
- It offers full control.
- Why it's wrong
- Adding fields to the main form is simpler, supported on mobile and needs no separate app.
Clue to watch for Users only need more fields on an existing record.
-
Personal view for everyone
- What candidates pick
- Change a personal view to update every dispatcher's list.
- Why it looks right
- It is quick to edit.
- Why it's wrong
- Personal views belong to one user; a system view is needed for shared columns and filters.
Clue to watch for All users need the same list.
-
Scheduled flow for real-time
- What candidates pick
- Run a flow every hour to catch new emergency work orders.
- Why it looks right
- Scheduling seems reliable.
- Why it's wrong
- An automated flow with a Dataverse trigger runs as soon as the row is created, avoiding delay.
Clue to watch for The alert must be immediate.
-
Standalone app for embedding
- What candidates pick
- Publish a standalone canvas app and link to it from Field Service.
- Why it looks right
- Canvas apps are familiar.
- Why it's wrong
- A custom page lives inside the model-driven app with its navigation and context, which is the supported embedding approach.
Clue to watch for Users should not leave the Field Service app.
-
Code for automation
- What candidates pick
- Write a plug-in to send notifications on booking completion.
- Why it looks right
- Plug-ins run server-side.
- Why it's wrong
- A cloud flow meets a notification need with configuration and is easier for a functional consultant to maintain.
Clue to watch for The task is a notification or simple record update.
Answer framework
For Domain 6 extension questions, choose the lightest Power Platform feature that meets the need.
- Check whether the need is about one record's layout, a list of records or where users navigate, and change the form, view or site map accordingly.
- Use system views for shared lists and keep personal views for individual preference, so changes reach the right audience.
- If a focused screen is needed inside Field Service, prefer a custom page; use a standalone canvas app when it must run separately.
- For actions triggered by data changes use an automated cloud flow, and use instant or scheduled flows only when the trigger matches.
- Package forms, views, apps and flows in a solution so the customization moves cleanly to test and production.
Practice question
Want more like this? The MB-240 practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
If you have used Power Apps before, this domain mostly needs a refresher framed around Field Service; if not, spend a few hours building simple examples. In a trial environment, create an unmanaged solution and add the work order table to it. Add a section and two fields to a copy of the work order main form, create a system view that shows high-priority unscheduled work orders, and add a subarea for that view to the Field Service app navigation. Open the app on mobile and confirm how the form change appears.
Next, create a small custom page that lists today's bookings for a selected technician and add it to the app's navigation. Then build an automated cloud flow that triggers when a work order row is added and posts a message when priority is high. Try an instant flow from a command button for comparison.
The exam rewards picking the simplest tool, so practice phrasing each requirement as layout, list, navigation, screen or automation before choosing. Keep a short decision table for this, and check it against practice questions until the choice feels automatic.
FAQ
How much of MB-240 was Implement Microsoft Power Platform?
Implement Microsoft Power Platform made up 5–10% of the final MB-240 outline, tied for the smallest share.
Is Field Service customized with Power Platform tools?
Yes. Field Service is a set of model-driven apps on Dataverse, so forms, views, navigation, canvas apps, custom pages and cloud flows are the standard extension tools.
When should I use a custom page instead of a canvas app?
Use a custom page when the screen should live inside the Field Service app and its navigation. Use a standalone canvas app when it needs to run independently.
What is the difference between a system view and a personal view?
A system view is shared with all users who have access to the table. A personal view belongs to one user and can be shared manually.
Which flow type reacts to a new work order?
An automated cloud flow with a Dataverse trigger for a row being added, optionally filtered by conditions such as priority or work order type.
Do form changes affect the mobile app?
Yes, when the form is used by the Field Service Mobile app module. Mobile forms are model-driven forms, so changes appear after the device syncs.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 6 knowledge
You have covered forms, views, navigation, canvas apps, custom pages and cloud flows. See whether you can pick the simplest tool for each Field Service requirement.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the MB-240 AI tutor Get any concept explained your way