MB-240 cheat sheet

Work order types set the default incident type, work order number prefix, and default service tasks; a work order can have only one work order type.

Incident types bundle service tasks, products, services, and skill requirements; adding one to a work order copies its lines as editable records.

Bookable resource types include User, Contact, Account, Equipment, Crew, Facility, and Pool; the type controls how the resource is scheduled.

Territories group resources and work orders geographically; the Schedule Assistant uses the work order territory to filter candidate resources.

Functional locations model a customer site hierarchy such as site, building, floor, and room; customer assets are equipment placed at a functional location.

Default booking statuses include Scheduled, Traveling, In Progress, On Break, Completed, and Canceled; status transitions can drive mobile app behavior.

Field Service settings control organization-level behavior such as work order numbering, default booking duration, geocoding, and push notifications.

Field Service security roles include Administrator, Dispatcher, Resource, and Inventory; a user needs a linked bookable resource record to receive bookings.

Work order system status values are Open, In Progress, Completed, Posted, and Canceled; status reasons provide detailed sub-status information.

Work order products track estimated and actual quantities and amounts; work order services track billable labor with duration and estimated or actual amounts.

Customer assets store product, serial number, warranty dates, parent asset, and functional location; asset history links prior and current work orders.

Adding an incident type copies its service tasks, products, and services to the work order; later edits to the incident type do not update existing work orders.

Agreements generate recurring work orders and bookings from agreement booking dates; incidents on the agreement define the work order template.

Posting a work order applies the posting configuration to create invoices, update inventory, and close the work order as read-only.

Work order priority drives scheduling order and can be used by the Schedule Assistant and Resource Scheduling Optimization as a constraint or goal.

Work order summary fields roll up total duration, total products, and total services from the related work order lines.

The Schedule Assistant returns available resources for an unscheduled requirement based on duration, territory, skills, roles, and promised time window.

Dragging an open requirement onto a resource cell creates a booking; dragging an existing booking moves or reassigns it.

Booking status changes such as Traveling and In Progress can update the work order system status and trigger Power Automate flows.

Resource Scheduling Optimization automates booking creation and reassignment by using a scope of resources and requirements plus defined goals and constraints.

Travel time is calculated from the resource start location to the work order location; actual travel duration can be captured on the mobile app.

Crew resources schedule multiple resources as one booking; each crew member must also exist as an individual bookable resource.

Promise time windows restrict scheduling; the Schedule Assistant only returns resources that can meet the promised from and to times.

The schedule board open requirements panel lists unscheduled work orders, and dispatchers can save filtered views for recurring dispatch scenarios.

Resource characteristics and roles are matched against work order requirements; the Schedule Assistant filters out resources that do not meet them.

The Field Service mobile app is a Power Apps model-driven app; technicians sign in and see bookings for their linked bookable resource.

Offline data is controlled by a Mobile Offline Profile assigned to the user; only tables and records in the profile are available offline.

The mobile app supports barcode scanning for products and customer assets, photo capture, and customer signature capture.

Work order service tasks appear as checklists; technicians mark tasks complete and can capture estimated versus actual duration.

Booking status changes in the mobile app can update work order status and trigger Power Automate flows.

Push notifications alert technicians to new or changed bookings and require configuration in Field Service settings and the mobile app.

The mobile app can capture time entries and work order products used; offline changes upload to Dataverse during synchronization.

Field Service mobile configuration controls offline sync interval, map display, barcode scanning, and branding.

Field Service inventory uses warehouses, product inventory records, and inventory transactions; available quantity equals on-hand quantity minus allocated quantity.

Inventory adjustments increase or decrease on-hand quantity; inventory transfers move product stock from a source warehouse to a destination warehouse.

Purchase order statuses include Draft, Submitted, Received, Billed, and Canceled; receiving a purchase order increases product inventory in the destination warehouse.

RMA records manage customer returns; the RMA receipt process returns products to inventory or marks them for credit or replacement.

Work order products can be allocated to a work order or marked as used; using the product consumes inventory and records actual quantity.

Vendors are required on purchase orders, and vendor price lists can supply default product costs.

Inventory transfers from a technician truck warehouse to the main warehouse return unused stock after service work.

Product inventory records are unique per product and warehouse and store on-hand, allocated, and available quantities.

Field Service data is stored in Microsoft Dataverse; Dataverse security roles, business units, and teams control record access.

Power Automate flows can trigger on work order creation, booking status changes, or purchase order approval and then run actions on Dataverse records.

Power BI provides Field Service analytics; the Field Service Analytics app includes work order, resource utilization, and inventory reporting.

Connected Field Service uses Azure IoT Hub and device telemetry to create IoT alerts and work orders from connected equipment.

Canvas apps and model-driven apps can extend Field Service; Power Apps Component Framework controls customize mobile app forms.

Business process flows guide users through work order stages and can map stages to work order status values.

Managed Power Platform solutions are locked for customization, support clean application lifecycle management, and are deployed to production.

Environment security uses Dataverse security roles, teams, and business units; users need appropriate Field Service roles and app access.