Releases/Winter 2026
| Warning | Work in progress! We are in the process of updating the information on this page. Subject to change. |
The 19.0 / Winter 2026 release is planned for January 2026. Find the download links for the latest preview version on the Preview page.
Modernized questionnaires available for public preview
New generation of questionnaire player brings new features, modern UI, and better integration options. See Modernized Questionnaire Player for details.
Whitelist new Resco web services
We are now going forward with the change announced one year ago. The fully qualified domain name (FQDN) of the Resco license server is changing from iservices.resco.net to svc.resco.net. If you are using a firewall to block outgoing communication, you need to add the new FQDN to its whitelist:
svc.resco.netsvc-01.resco.netsvc-02.resco.net
The current FQDN iservices.resco.net remains active for some time to help you with the transition.
IP addresses
Some network infrastructure can require IP addresses rather than domain names. The IP addresses are managed by Microsoft Azure and may change over time. You can download them from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=56519
Alternatively, you can download the list of FQDNs and IP addresses from Resco in JSON format. This download also includes the IP addresses for outbound communication. It is cached and updated every 4 hours.
- https://svc-dev.resco.net/network/allowlist (temporary list)
- https://svc.resco.net/network/allowlist (future permanent list)
Whitelist Sentry ingestion endpoints
Resco is utilizing Sentry to monitor the performance of Resco Mobile CRM and report issues without requiring user interaction. This helps us deliver fixes before customers report them.
Sentry is changing its ingestion IP addresses. If your infrastructure blocks outbound IP traffic, please use the following guidance to unblock Sentry's ingestion endpoints.
Changes in form design
In the NEXT release after this one, we're changing the structure of entity forms in Resco Mobile CRM. We're going to combine flexible forms and tabbed interface: Each form can have one or more tabs, each tab can have one or more cards.
In THIS release, to prepare for this change, we are deprecating some settings in Woodford configuration and Resco Mobile CRM Setup/Settings (see the details of the deprecation). Contact Resco support if you want to enable legacy behavior for your organization.
More details for calendar entries
The calendar entries in Resco Mobile CRM can now display additional details about appointments. In the calendar configuration in Woodford, you can now define a card with up to 3 fields for each view available in the calendar.
Optimized image size in inspection reports
Reports generated from questionnaires with multi-image questions now use a different image format (JPG instead of PNG). As a result, the generated reports are significantly smaller in size while maintaining sufficient image quality.
Rules: ShowToast
The new ShowToast function allows rule authors to display non-blocking toast notifications to users. Unlike the current Say Text function (which displays a modal window and requires the user to close it), ShowToast displays a brief, automatically disappearing notification, reducing unnecessary user interaction.
Simpler localization of commands
Woodford editors no longer have to memorize the exact string IDs (or check the wiki) to localize form commands. On the command management screen, select any command and click Change Localization. You can then directly change the translations of the selected command.
Preload iframes
On the Microsoft Store version of Resco Mobile CRM, loading forms with iframes is often slow. Initializing new Edge WebView2 containers can take a significant amount of time. We're introducing the option to optimize the process by preloading the container and reusing it for multiple iframes. The behavior is available for iframes on forms (with Visible = No), views, charts, calendar, and route plan.
Bulk update enhancements
We are making bulk record updates much more powerful and flexible. If you haven't tried bulk updates before, now is a great time to add this feature to your projects.
- You can define the order in which the records are processed.
- By default, bulk updates run in parallel. You can now enable sequential processing for scenarios where execution order matters.
- You can now choose between guided and silent modes: "Guided" requires user confirmation on every step, while "Silent" only prompt questions when errors or warnings occur.
- In addition to the default "Update" mode for modifying records, we're introducing the "Action" mode for creating new records or performing other actions that don't modify existing records.
CurrentUser fetch macro: Dynamic filtering of records from virtual tables
Since this release, a fetch macro @@{{currentuser.columnname}}@@ is available to build fetch conditions based on the values of fields on the systemuser record of the current user. This feature is only available for the Dynamics/Dataverse backend.
This can be useful in specific niche scenarios, such as building sync filters to return only records related to the current user on external (virtual) tables where there is no owner lookup column (e.g., integrations with Business Central, F&O, or SAP). In such cases, admins can define a custom externaluserid column on systemuser table, prefill the column with the user identifier from an external system, and use it in the sync filter like this:
<fetch>
<entity name="account">
<filter>
<condition attribute="extid"
operator="eq"
value="@@{currentuser.externaluserid}@@" />
</filter>
</entity>
</fetch>
We're introducing a new setting to Woodford's app project Configuration: Max Sync Shared Records on the Offline Data Sync tab. This applies only to Salesforce. Similar to Max Sync Records, it sets a limit on the number of shared records that can be downloaded per entity. This limitation is imposed for performance reasons and to avoid excessive API consumption. Due to Salesforce API limitations, shared records are downloaded in batches of approximately 180 records, so downloading 10,000 records results in approximately 55 web requests. Only increase this number if sync longs contain a warning that the limit is reached and you are unable to decrease the number of shared records on the server side.
Note that users can also override this value in the mobile app via Setup: scroll to the Synchronization section and modify Max shared records synced per entity as needed.
Show/hide push notifications about completed sync
Woodford admins as well as users of Resco Mobile CRM can now decide if they want to see notifications about completed synchronizations. In Woodford project Configuration and in Resco Mobile CRM's Setup, use the new option Show notification when sync finished.
Before this change, the notification was always displayed, except on Windows devices. In general, we recommend keeping notifications enabled. However, in scenarios involving frequent background synchronizations, too many notifications can be disruptive.
