Find information on Release 11.1.0.8 (June 2026) of Rental Mobile Operations - Field Service app.
Version information:
Product | Version | Minimum version | Latest validated version | Planned next |
|---|---|---|---|---|
Rental Mobile Operations - Field Service app | 11.1.0.8 | D365 F&SCM 10.0.45 STAEDEAN Rental Management 10.0.48.60 | D365 F&SCM 10.0.48 | September 2026 |
General release information
General release information on Release 11.1.0.8 (June 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. It also describes 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 selling and implementing as well as customers who have bought the solution.
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 for Finance and Supply Chain Management instance in order to be fully compatible. The following table lists such dependencies.
Rental Mobile Operations Field Service version | Dual-Write mapping Base version | Minimum required Rental Management version |
|---|---|---|
11.1.0.8 | 2.0.0.0* | 10.0.48.60 |
*Base version 2.0.0.0, but individual mappings are higher. It is expected that customer use 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 will not support the full capabilities of Rental Mobile Operations - Field Service app.
Note
As this is a complete 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 in 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.
More information about our latest available product versions, the latest validated GA-versions from Microsoft as well as the Minimum Microsoft version required, please visit this page: Release Information.
It could be that the screen needs to be updated as new information is 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 Svensk. More languages can be added, see for more information our Rental Mobile Operations - Field Service - Implementation Guide.
5. Apps
The Rental Mobile Operations - Field Service app works with Microsoft Power Apps application. See User Guide for more detailed information on installation and usage of this application.
Sales, Consultants and Customer 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 new added offline profiles that do not follow Microsoft's best practices are at the customer's risk and are not covered by support. See Implementation Guide for more information.
In the User Guide is clearly stated 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 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.
On top of a Managed Solution customization can be built, it is 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. See for more information 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/customizations have been made to dual-write a different version no. and publisher is 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 if an unmanaged solutions 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.
Date 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.
What’s new
No new or changed features are available in Release 11.1.0.8 (June 2026) of Rental Mobile Operations - Field Service app.
Note
Microsoft is continuously adding new features in to D365 F&SCM. Sometimes these are public preview and will be made generally available in future releases. In other cases, these changes are already general available, and you have the choice to activate them. Currently, STAEDEAN is not testing compatibility with all new features or combinations. Once a feature is enabled at your environment and in case of any issues or questions related to new standard features and our solutions, kindly contact us via STAEDEAN support.
Note
STAEDEAN Rental Management is frequently extended with new features. Many of these changes are not related to the Rental Mobile Operations applications. And not that not each related change is automatically supported by the Rental Mobile Operations applications.
Bug fixes
Bug fixes in Release 11.1.0.8 (June 2026) of Rental Mobile Operations - Field Service app.
Bug ID | Title | Description |
|---|---|---|
236786 | Timesheets | The Travel, Break and Extra categories set in the Work order parameters did not apply to timesheet lines created from the Field Service app. The timesheet category is now set the same way as hour journals. |
238149 | Synchronization | The initial sync of the Resource groups – employee services (ti_resources) dual-write mapping failed with an error. The plugin now reads the Business Unit dynamically in code instead of from a hardcoded step configuration, so the initial sync completes. |
239090 | Field Service app | The dynamic field/column component (DFM) in the Field Service app did not respond to resize actions. The field list is now wrapped in a flexible container that fills the available width, so columns resize as expected. |
239376 | Work orders | Users could manually change a work order in status Created in the Field Service app. All manual status options have been removed from the Status Reason dropdown on the work order form, so the status can no longer be changed. |
239782 | Hours | The project date on hour journal lines used the registration date instead of the actual hour line date. The project date is now derived from the from-date of the hour line created in Dataverse. Note: no extra lines are added when the duration spans more than 24 hours. |
239806 | Checklists | Adjusting a checklist in the Field Service app on a mobile phone showed a Discard and Save message. The form now saves automatically when the checklist result changes, so it no longer stays in an unsaved state. |
241097 | Timesheets | Opening a timesheet through the timesheet number from work order line transactions raised an error. Timesheet data is company specific while work order line transaction data is global, so the timesheet now opens in the correct company context. |
242523 | Synchronization | The ti_globalproducts dual-write mapping was missing from the Field service solution. The mapping has been added to the Field service solution so it is available independently. It is retained in the Transport solution, so Transport-only customers are not affected. |
243007 | Synchronization | Business object component data could not sync to the mobile app. The business object component data entity had no unique key on the F&O side, which prevented synchronization with the mobile app. As the first part of a two-release fix, the table RecId is added as a string field and mapped to a new field in Dataverse in this release; the key change follows in the September 2026 release. The new field data must be synced to Dataverse in all environments after deployment. |
243090 | Synchronization | The Current resource group membership (ti_resourcememberships) dual-write mapping synchronized resources that were not flagged as Mobile app users. The logic now inserts membership records only for mobile resources. To complete the fix, use the Excel add-in to delete any existing non-mobile resource records from the ti_resourcememberships table. |
243125 | Synchronization | Errors occurred during the initial sync of a dual-write mapping. The mapping has been corrected so the initial synchronization completes without errors. |
245706 | Synchronization | Assembled assets on a business object were not displayed in Dataverse or the mobile app, due to an incorrect dual-write mapping version. The mapping version for Business object components (employee services) has been corrected. This is a configuration-only fix. |
Known Issues
Known issues in Release 11.1.0.8 (June 2026) of Rental Mobile Operations - Field Service app.
1. Dual-Write
Microsoft is investing heavily in Dual-Write as synchronization tool, it is Microsoft's advice to use Dual-Write. 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 makes every 5 minutes a synchronization based on the found delta in data.
3. Standard features
In the Rental Mobile Operations apps are a lot of standard available Microsoft features visible, this does not mean that we support them. It could be that this feature is not working in relation with the application or is not working at all. In the User Guide is written down 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 will not say that the application will support all features in offline mode. In the User Guide is described 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, attempts will be made to indicate this in the User Guide.