Releases/Summer 2026
| Warning | Work in progress! We are in the process of updating the information on this page. Subject to change. |
The 19.1 / Summer 2026 release is planned for June 2026. Find the download links for the latest preview version on the Preview page.
Microsoft Store app transition to WinUI
In this release, we are introducing a major update to the Microsoft Store version of Resco Mobile CRM for Windows. The first public preview was released on March 30, 2026.
Microsoft officially deprecated Universal Windows Platform (UWP) in 2021. While we have continued to maintain the UWP-based Microsoft Store version of Resco Mobile CRM, ongoing development has become increasingly difficult as some underlying components are no longer receiving security updates. To ensure long-term stability, security, and compatibility with modern Windows technologies, the Microsoft Store version of Resco Mobile CRM will transition from UWP to a new WinUI-based application.
What does this mean for Microsoft Store users?
- The current UWP application will be seamlessly replaced by the new WinUI version via the Microsoft Store.
- The new app will continue to provide the same core functionality while enabling future improvements built on modern Windows frameworks.
- No manual action will be required for most users.
- For users with Microsoft Dataverse/Dynamics/Power Platform that connect using the MSAL mode, we strongly advise to synchronize their app after the upgrade. Synchronization requires user to sign in once more. Without synchronizing, the data might be unavailable in online mode.
WebView changes
| Important | The new WinUI application will support Microsoft Edge WebView2 only. We have announced the deprecation back in 2024. |
As a result:
- Legacy WebView will no longer be supported in the Microsoft Store version.
- Customers using custom business logic or components optimized for the legacy WebView should migrate to WebView2.
How do you check if you are using the legacy WebView?
- Edit the app project in Woodford, go to Configuration, and search for "edge".
- If Use Edge WebView2 is set to "True", you are not impacted.
The transition from UWP to WinUI (and the related transition from legacy Edge WebView to modern WebView2) does not affect the app's native UI or its synchronization or communication with the server.
The only impact it might have on custom offline HTML components and hidden iframes included in your customization. As WebView2 is a (huge) superset of WebView (which was based on the ancient Edge v8 engine), we do not expect any missing functionality. However, we can't guarantee that the behavior of your JavaScript code will be exactly the same after the transition. For example, security policies like CORS are a lot stricter. We have done all steps from our side to ensure full compatibility of the JavaScript Bridge with both browsers. The only requirement is using JSBridge version 16 or later.
The only known advantage of the old WebView is that, being very small, it has much lower loading times. Therefore, we recommend identifying the places where multiple iframes (visible or hidden) are loaded and verifying that the overall performance isn't affected. If you observe any performance issues, please contact us with details, and our development team can prepare recommendations to reduce the performance impact.
Temporary fallback option
For organizations that require additional time to migrate:
- We can provide a legacy Windows Store UWP version that still supports the legacy WebView.
- This version will receive limited updates and no access to new features after release 19.1 and is intended as a temporary transition solution.
We strongly recommend performing the migration to WebView2 to ensure full compatibility with future releases of Resco Mobile CRM.
- To switch to the legacy UWP app, all users have to
- Synchronize their Resco Mobile CRM app to make sure all local changes are uploaded to the backend server.
- Uninstall Resco Mobile CRM.
- Install Resco Mobile CRM Legacy.
- Perform the initial synchronization.
A similar switch will be necessary if you later modify your business logic and want to return to the standard Microsoft Store app.
- Delay update, stay with 19.0 app
- Mobile app users can pause Microsoft Store updates for up to 5 weeks.
- If your organization has managed devices, your administration probably has additional options to delay or disable updates.
New questionnaires
We have introduced multiple new features for the Modernized Questionnaire Player (gen 2).
Table view
You can now display question groups as tables. This function is available for second-generation questionnaires only.
Barcode scanning
The second generation of questionnaires now supports barcodes. In Gen 2, barcode is no longer a standalone question type; it can now be enabled for questions of the types Text, Number, URL, Email, and Lookup. Barcodes are not supported on Power Pages.
TOC/logo customization
You have more control over the cover page of your questionnaire. Control the logo's size and choose how it fits within its container. Or hide logo or table of content completely.
Power Pages: getQuestionnaireIdByTemplateName function
getQuestionnaireIdByTemplateName(templateName: string, []?: ["published", "draft", "staged", ...]
We're introducing a new way to access templates in Power Pages. This function retrieves the latest published version of a template.
- As the first parameter, use the template name.
- The second optional parameter overrides the published statuscode of the searched questionnaire.
On the page with the latest Questionnaire Player component, the function can be accessed like this:
const questionnaireId =
await window.Resco.Questionnaires
.getQuestionnaireIdByTemplateName("My Template", ["published", "draft"]);
Mobile reports: special visibility behavior for the first page
A frequent use case when designing a multi-page document: hide the header and footer on the first page. We are now bringing this feature to mobile reports. For any cell on your report, you can now use a special built-in variable {IsFirstPage} in the Visibility property. It returns "true" only on the first page.
Important: This feature is only available for PDF reports; for other formats, IsFirstPage is always true.
Headsup: Exchange Web Services end of service
Microsoft announced that Exchange Web Services (EWS) is approaching end of service in Microsoft 365 and Exchange Online. Microsoft plans to disable EWS in October 2026 and a complete shutdown of EWS in 2027. See Microsoft blog for more details.
Resco will provide a replacement API access to Exchange later this year. Meanwhile, to make sure you don't lose access, consider setting EWSEnabled to "true" as detailed in the Microsoft blog.
Salesforce: faster metadata update
The Update Metadata function in Woodford for Salesforce is much faster for organizations with a large number of users and profiles. This is because instead of deleting and re-importing the entire set of users, roles, and privileges, Resco now calculates and applies only the differences between the state on Salesforce and Resco Cloud.
Salesforce API 66.0
Resco now supports Salesforce API 66.0 (Spring 2026).
Woodford CLI: Support for client ID and client secret
In addition to the device authentication flow, Woodford CLI can now authenticate using client ID and client secret. This can be useful, for example, when you want to automate deploying the same app project to multiple customer environments.
Improved error reporting for workflow rules
Error messages displayed while executing rules in the Resco Mobile CRM app (views, forms, questionnaires, route planner, calendar) now include detailed information about failures, including the step, line, record, and exception message, instead of generic messages or silent logging. Errors in row script and calendar rules are now surfaced to users (once per list refresh / calendar reload), reducing confusion and support requests. This change does not apply to deprecated components such as the web app and Schedule Board.
