Release 11.1.0.25 (October 2026) - Field Service app

General release information on Release 11.1.0.25 (October 2026) of Rental Mobile Operations - Field Service app.

1. Purpose

These release notes cover new functionality, capabilities, and known issues for Rental Mobile Operations - Field Service app in this release. They also describe the underlying application structure.

Product and implementation consultants familiar with Rental Mobile Operations - Field Service app form the primary audience.

2. Audience

The audience for these release notes is certified partners who sell and implement the solution, as well as customers who have bought it.

3. Compatibility

In some cases, an update of Rental Mobile Operations - Field Service app requires an update of the STAEDEAN Rental Management version of the linked Microsoft Dynamics 365 Finance & Supply Chain Management instance in order to be fully compatible. The following table lists such dependencies.

*Base version 2.0.0.0, but individual mappings are higher. Customers are expected to use the highest available versions.

The Rental Mobile Operations - Field Service app continues to work on older versions and can be implemented on older Dynamics 365 Rental F&SCM versions. However, this does not support the full capabilities of Rental Mobile Operations - Field Service app.

Note

As this is a completely new application with a new data structure, this application will not work on older versions of D365 F&SCM. It operates from version 10.0.40.52 (July 2024) onwards.

In case of an Error, STAEDEAN may provide a Hotfix on a reasonable efforts basis in a way it considers appropriate at its discretion. STAEDEAN cannot be obliged to provide Hotfixes if Client has not deployed the latest Release or the Release second to the latest Release and/or is not using a supported version of D365 F&SCM.

To ensure our customers can fully leverage the latest enhancements, features, and quality improvements, we are committed to providing increased support by keeping them updated with the most recent releases. Our data indicates that customers on the latest version experience fewer issues and requests, demonstrate greater resilience, and effectively enhance their organizational efficiency.

For more information about our latest available product versions, the latest validated GA-versions from Microsoft as well as the Minimum Microsoft version required, see Release Information.

This page may be updated as new information becomes available. As a supplier, we assume that delivered solutions and upgrades are first tested in a test environment and deployed to a live/production environment after internal customer approval.

4. Languages

The Rental Mobile Operations - Field Service app is delivered in English (US, default language), Nederlands, Deutsch, Dansk, Norsk (Bokmål) and Svenska. More languages can be added. For more information, see our Rental Mobile Operations - Field Service - Implementation Guide.

5. Apps

The Rental Mobile Operations - Field Service app works with the Microsoft Power Apps application. See the User Guide for more detailed information on installation and usage of this application.

Sales, consultants, the customer's IT department, and customer procurement should also pay attention to the Power Apps system requirements documentation as this gives information on supported devices and versions.

6. Offline capabilities

The app is designed with Microsoft offline-first mode and built following Microsoft best practices on how much data is downloaded and the speed of downloading this data to a mobile device based on an offline profile.

Creating a new offline profile and assigning it to users is possible but could cause performance issues on the used mobile device. Changes to existing or newly added offline profiles that do not follow Microsoft's best practices are at the customer's risk and are not covered by support. See the Implementation Guide for more information.

The User Guide clearly states which features are supported in offline mode.

7. Managed Solution

The Rental Mobile Operations - Field Service app is delivered as a managed solution. Managed solutions are deployed to any environment that isn't a development environment for that solution. This includes test, UAT and production environments. Managed solutions can be serviced independently from other managed solutions in an environment. As an ALM best practice, managed solutions should be generated by exporting an unmanaged solution as managed and be considered a build artifact.

Additionally:

• You can't edit components directly within a managed solution. To edit managed components, first add them to an unmanaged solution. When you do this, you create a dependency between your unmanaged customizations and the managed solution. When a dependency exists, the managed solution can't be uninstalled until you remove the dependency.

• You can't view the managed properties.

• You can't export a managed solution.

• When a managed solution is deleted (uninstalled), all the customizations and extensions included with it are removed.

Some important remarks:

• You can't import a managed solution into the same environment that contains the originating unmanaged solution.

• To test a managed solution, you need a separate environment to import it into.

• When you delete a managed solution, the following data is lost: data stored in custom entities that are part of the managed solution and data stored in custom attributes that are part of the managed solution on other entities that are not part of the managed solution.

Customizations can be built on top of a managed solution. They are deployed as an unmanaged solution. If problems arise with the app, the first thing that will be considered is whether there are unmanaged solutions present in the environment in addition to the managed solution. If this is the case, the first thing to consider will be whether they have a negative impact on app performance. For more information, see our Power Platform Managed vs Unmanaged Solutions document.

8. Modifications

With each release an updated Mappings file (zip file with Excel files) is delivered with an overview of all mappings. This gives an overall view of all the mappings used by the app.

In D365 F&SCM all running dual-write mappings are shown with their corresponding version and publisher. This way it is clear what the latest version is and who it came from. If modifications or customizations have been made to dual-write, a different version number and publisher are shown.

Customizations to the app are recognized as unmanaged solutions. When an upgrade is done to a new managed version, newly added features could be blocked by an unmanaged solution. Customers can check new features based on notes in the release notes and can decide whether an unmanaged solution must be altered or deleted to give access to new features.

9. Time zone explanation

The app is linked to Dataverse and Dataverse is linked to STAEDEAN Rental Management, which affects the display of date and time.

Dates and times in Dataverse are always based on the UTC time zone. If no date and time are entered, 1/1/1900 12:00 AM will be stored in Dataverse. All date and time columns in Dataverse support values as early as 1/1/1753 12:00 AM.

The STAEDEAN Rental Management user must have the same time zone setting as the app user to see the correct date and time that is coming from the app to STAEDEAN Rental Management.

New or changed features in Release 11.1.0.25 (October 2026) of Rental Mobile Operations - Field Service app.

Note

• Microsoft is continuously adding new features to D365 F&SCM. Sometimes these are in public preview and will be made generally available in future releases. In other cases, these changes are already generally available, and you have the choice to activate them. Currently, STAEDEAN is not testing compatibility with all new features or combinations. If you enable a feature in your environment and have issues or questions about new standard features in combination with our solutions, contact STAEDEAN support.

• STAEDEAN Rental Management is frequently extended with new features. Many of these changes are not related to the Rental Mobile Operations applications. Note that not every related change is automatically supported by the Rental Mobile Operations applications.

1. Feature 233551: Work order sign-off report

When you complete a booking and confirm a work order task sign-off, a sign-off report is created as a PDF file. The sign-off report is attached to the work order line in D365 F&SCM and sent by email to your contact right after the sign-off. A sign-off report is created for each completed work order task.

The sign-off report shows the work order details, checklist results, meter readings, parts, hours, other costs, and the signature of your contact.

See also: Sign off work order task.

2. Feature 224611: AI Inspection

You can perform an AI inspection to detect damage on an asset. You take pictures of the asset and send them to the AI damage detection agent. The agent returns the damages it found, with a severity, a summary, and a recommendation.

With the AI inspection, you can:

• Start an AI inspection from a work order task (booking): The AI inspection is automatically connected to the work order of the booking.

• Start an AI inspection from an asset: Use the new AI Inspection tab on the Asset page. This tab shows all AI inspections of the asset.

• Add a picture for each side of the asset: Front, Back, Left, Right, Top, and Bottom. For each damage, the picture on which it was found is shown.

• Review the damages found: The damages are compared with the latest processed AI inspection of the asset. This way, you can see which damages are new.

• Give your assessment of each damage found.

• Create a work order to have the asset repaired: You can create one work order for each AI inspection that is not yet connected to a work order.

The AI damage detection agent uses the object name of the asset. If the asset information is not sufficient for the agent, a warning is shown on the Asset page.

The AI Inspection agent is included in the standard Equipment Rental offering, free of charge in its first iteration, starting with the October 2026 release. It is natively integrated with Rental Mobile Operations - Field Service app. It can also be integrated with custom applications on Azure and Power Platform. For more information, contact us.

See also:

• Perform AI inspection

• Perform AI inspection from work order task

• Perform AI inspection from asset

• Release 10.0.49.61 (October 2026) (STAEDEAN Rental Management release notes: What’s new > Feature 224611)

Bug fixes in Release 11.1.0.25 (October 2026) of Rental Mobile Operations - Field Service app.

Known issues in Release 11.1.0.25 (October 2026) of Rental Mobile Operations - Field Service app.

1. Dual-write

Microsoft is investing heavily in dual-write as a synchronization tool and advises using it. Dual-write is a near real-time (1-10 seconds) solution. However, dual-write can still be "slow" as some synchronizations take a minimum of 5 seconds. Also, dual-write has its limitations, known issues and unsupported features which are described in the Mapping Concept pages of dual-write, see the Dual-write home page.

2. Synchronization time

The Rental Mobile Operations uses standard Microsoft technology to synchronize. This technology synchronizes every 5 minutes based on the data changes (delta) it finds.

3. Standard features

Many standard Microsoft features are visible in the Rental Mobile Operations apps. This does not mean that we support them. Such a feature may not work with the application, or may not work at all. The User Guide describes which standard Microsoft features are supported by the application.

4. Offline mode

The Rental Mobile Operations apps are based on offline-first features from Microsoft for model-driven Power Apps applications. However, this does not mean that the application supports all features in offline mode. The User Guide describes which features are supported in offline mode. In addition, it could be that some standard Microsoft features do not work in offline mode. Where known, we will try to indicate this in the User Guide.