Dynamics 365 Field Service Mobile Notes: Setup Guide, Offline Use and Multi-File Upload Behavior

Having moved through public preview in June 2026 and reached general availability in August 2026 across Worldwide Standard Multi-Tenant cloud environments, this Power Apps component framework (PCF) control is now marked as launched on the Microsoft 365 Roadmap. However, because it is an opt-in, UI-level framework component, it will not magically appear on your technicians' devices overnight. Administrators and makers must manually add and configure it per entity form in Power Apps. Here is a complete look at how the control works under the hood, its quirks with multi-file media uploads, and how to deploy it across your mobile forms.

What the Mobile Notes Control Actually Does​

In a standard Dynamics 365 model-driven environment, notes share space inside the multi-purpose Timeline control alongside emails, appointments, phone calls, and system posts. While comprehensive for a dispatcher sitting in front of dual 27-inch monitors, that unified feed can feel cumbersome when a technician on-site just needs to snap a photo of a corroded valve or read the last technician's troubleshooting notes.

According to Microsoft's roadmap documentation and the Dynamics 365 IT Professional blog post by Product Manager Heer Patel and Principal Program Manager Jonathan Baker, the Mobile Notes control strips away the surrounding noise to focus strictly on note-type activities. Other activity types are ignored in this view, though the notes themselves are still written directly to the underlying annotation table (the exact same Dataverse table used by the standard Timeline). That architectural decision is critical: frontline technicians get a dedicated, touch-optimized interface on their devices, while back-office dispatchers and managers working on the web continue to see those exact same notes populate seamlessly inside their standard Timeline view.

Key capabilities of the control include:

• In-form media and text capture: An overlay screen lets technicians input text alongside image and video uploads directly within the entity form.
• Optimized consumption: A dedicated "notes wall" renders rich previews and improves text readability for quick scanning on the job.
• Offline resilience: As detailed in Microsoft's June 2026 Field Service mobile update blog, the control supports offline capture in low- or no-connectivity environments, syncing data back once connectivity is restored.
• Platform boundaries: While Microsoft's broader wave of Field Service mobile improvements targets iOS, Android, and Windows devices, Microsoft Learn documentation for the Mobile Notes control specifically notes that it is supported only on mobile and tablet. While the component might technically function in a web browser, web use is unsupported, and the roadmap entry notes that it does not change the standard web experience.

The Multi-Media Upload Quirk​

Before rolling this out to a fleet of technicians who love taking dozens of job-site photos, administrators need to understand one very specific implementation detail documented on Microsoft Learn.

While the interface allows a user to create a note and select multiple images or videos during a single capture flow, the app creates a separate note record for each uploaded file, duplicating the same title and body text across each one. If a technician attaches four photos to a single note entry titled "Damaged compressor housing," Dataverse will store four individual annotation records with that identical title and text, each holding one photo.

Why does this matter? If you have downstream Power Automate flows, custom plugins, or reporting dashboards triggered on annotation record creation, a single multi-photo submission from the field will fire that trigger multiple times. Makers and system architects should test their automation logic against this behavior before deploying the control to production.

Configuration Options: Display Modes and Record Association​

When makers add the Mobile Notes component to a form in Power Apps, it is not a one-size-fits-all widget. Microsoft Learn documentation outlines two primary configuration properties that dictate how technicians interact with it: Display mode and Attach to.

The Attach to setting is particularly helpful for complex field workflows. For example, if a technician is working inside a nested sub-form or component tied to a parent Work Order or Bookable Resource Booking, setting Attach to to Top Level Form ensures that critical documentation rolls up to the primary parent record rather than getting buried in a child entity where back-office staff might miss it.

Step-by-Step Guide: How to Enable Mobile Notes on a Form​

Because this is a UI-level framework control, no tenant-wide feature flags are required. However, because Power Apps component framework controls bind to form fields, you must bind the Mobile Notes control to an optional text column on your target form.

According to Microsoft Learn, here is the exact procedure to set it up:

1. Check table prerequisites (for custom tables): If you are configuring notes on a newly created Dataverse table, ensure that the Enable attachments (including notes and files) checkbox is selected during table creation.
2. Create a binding column: Open Power Apps and navigate to the app and table where you want to enable mobile note-taking. Add a new data column with the Data type set to Single line of text and the Required setting set to Optional.
3. Add the column to your form: Open the target entity form in the Power Apps form designer and place your newly created text column into the desired section of the form.
4. Hide the column label: Select the column on the form canvas. In the right-hand properties pane under Display options, check Hide label so the placeholder text field's label does not clutter the mobile UI.
5. Add the Mobile Notes component: With the column still selected, locate the Components section in the properties pane and select + Component.
6. Configure the control: Search for and select the Mobile Notes control. Configure your preferred Display mode (All, Add Notes, or Notes Wall) and Attach to behavior (Current Form or Top Level Form).
7. Publish and sync: Select Save and publish on the form. Frontline workers will see the updated interface on their mobile devices after their next app sync.

If your team decides the new workflow isn't a fit, reverting is painless: Microsoft's roadmap documentation notes that you simply remove the control from the form in Power Apps, save, and republish.

Practical Context for Admins: How Does This Fit Existing Field Service Notes?​

Veteran Dynamics 365 administrators may reasonably ask: Didn't the Field Service mobile app already have a dedicated Notes experience?

Yes, in specific contexts. Standard Field Service mobile configurations have long included a booking-specific Notes tab on the Bookable Resource Booking form that supports text, optimized images, audio, and video notes (which requires security-role permissions to the msdyn_bookableresourcebookingquicknotes table).

What makes the new Mobile Notes PCF control distinct and practical is its flexibility across entity forms and its direct integration with standard Dataverse annotations (annotation table) and the Timeline. Rather than being locked to booking quick notes, makers can drop the Mobile Notes control onto any attachments-enabled table form where technicians spend their time, customize whether it acts as an input button, a reading wall, or both, and control parent-child record rollups on nested forms.

For IT teams looking to reduce frontline friction without breaking back-office visibility, it is a clean, low-risk customization worth testing in a sandbox environment today.