Please find details below of the items included in this latest release.

An enhancement has been introduced so that manual equipment creation can now be tied directly into journals. When enabled, a PA Code is required when adding new equipment, and the selected PA Code is saved on the equipment record.Once a valid PA Code is chosen, a journal entry is created automatically for the new equipment, using the correct nominal accounts and a clear “Equipment Added” description. This keeps manually added equipment in line with catalogue‑ and purchase‑order‑based equipment for financial tracking.

F-Gas form validations blocked users from continuing when entered charge values did not match the expected system or cylinder values. This has now been improved by adding a bypass validation option to the Amount widget, allowing the validation message to remain visible as a warning while still letting engineers continue and complete the form without being stopped.

F‑Gas refrigerant charge fields have been updated to use clearer terminology. “Capacity” now refers to the maximum refrigerant the system or cylinder can hold, and “Remaining Capacity” refers to how much space is still available.These labels are applied consistently across forms, widgets, messages and data screens, making refrigerant charge information easier to understand at a glance.

A new expiry‑date column has been introduced on stock screens so expiry information for items is clearly visible during everyday checks.A daily notification alert now highlights items that are expiring within the next 30 days or already expired, with a link into a filtered stock list showing these items, making expiry‑sensitive stock easier to review and manage.

The system did not support several CAD drawing file formats, limiting users from uploading design files.Support has now been expanded to include:
.dwg, .dxf, .dwt, .dgn, .dwf, .dwfx, .step, .stp, .iges, .igs, .satUsers can now upload multiple CAD files successfully across the system.

When a Work Done Note created from the Mobile App by an Engineer was updated by a Web user, the Job details showed only the Web user’s name, overriding the original creator.This has been enhanced to correctly display:

Created By → Engineer who created the note via Mobile

Last Updated By → Web user who last updated the note

This ensures accurate tracking of note creation and updates.

Service Contract Invoices report in the web portal included an Invoice Type filter that was not required and could cause confusion when users were reviewing service contract invoice data. This has now been improved by removing the Invoice Type filter from the report, giving users a cleaner and more relevant reporting experience when accessing Service Contract Invoices in the web portal.

Hire Contract Invoice report in the web portal included an Invoice Type filter that was not needed, and the existing Service Contract filter label did not clearly match the report purpose, which could confuse users when selecting contract-based data. This has now been improved by removing the Invoice Type filter and renaming the Service Contract filter to Hire/Rental Contract, making the Hire Invoices report clearer, more relevant, and easier for users to understand and use.

Job Invoices report in the web portal included an Invoice Type filter that was not required and could add unnecessary complexity when users were reviewing invoice information. This has now been improved by removing the Invoice Type filter from the report, giving users a simpler and clearer experience when accessing Job Invoices in the web portal.

Equipment Deal Invoices report in the web portal included an Invoice Type filter that was not required and could create unnecessary confusion when users were reviewing invoice data. This has now been improved by removing the Invoice Type filter from the report, providing a cleaner and more relevant experience for users accessing Equipment Deal Invoices in the web portal.

We’ve improved the way invoice data is mapped for the Iplicit integration to ensure greater accuracy and consistency. Invoice dates are now correctly based on the transaction date, and description and customer reference fields are properly populated during posting. Additionally, values are now aligned with system limits to prevent data issues. These enhancements improve the reliability of financial data transferred to Iplicit and ensure better alignment with accounting expectations.

Sales Order Invoices report in the web portal displayed an Invoice Type filter that was no longer needed and could cause confusion when reviewing invoice data. This has now been removed, making the report clearer and easier for users to navigate.

Miscellaneous Invoices report in the web portal displayed an Invoice Type filter that was no longer needed and could create confusion when reviewing invoice data. This has now been removed, making the report clearer and easier for users to use.

We’ve fixed an issue where the correct validation message was not shown when raising a purchase order with a quantity greater than the requested amount in a Part Request. Although the system correctly prevented the action, the missing message could cause confusion for users. The appropriate validation message is now displayed, clearly informing users when the entered quantity exceeds the allowed limit.

We’ve fixed an issue where the Parts tab in Job Details could take an unusually long time to load and eventually time out. In some cases, this prevented users from viewing or working with parts information for a job. The loading process has now been optimized, ensuring the Parts tab opens quickly and reliably, improving overall performance and usability when managing job details.

We’ve fixed an issue where adding equipment through ESS (Equipment Service Schedule) did not correctly attach to an existing job when selected. Previously, even when users chose an existing job, the system would create a new job instead, causing the selected job to be ignored. This has now been resolved, and schedules are correctly added to the selected existing job, ensuring the process behaves as expected and avoids unnecessary duplicate jobs.

Previously, stock was updated in the Engineer Van location without requiring approval when the adjustment value limit was set to zero. The behavior has now been aligned to ensure consistent and controlled stock update handling during manual stock receipt scenarios.

We’ve fixed an issue where creating a job quote for certain customers could result in an error and prevent the process from completing. In some cases, selecting a customer would trigger an unexpected error, blocking users from proceeding with the quotation. This has now been resolved, and job quotes can be created successfully for all customers without interruption.

Previously, Order Acknowledgement and Delivery Note reports did not reflect the bin location for items, which made it harder for users to identify the correct stock location from the generated documents. This has now been improved so that bin location information is correctly shown on both reports, giving users clearer and more complete order documentation.

Mobile:
On the iOS mobile app, the Day Summary Enquiry screen was always showing the task number as “0” next to each job number, instead of displaying the real task reference. This made it hard to tell which specific task on a job each line referred to.
​
The Day Summary Enquiry view has been corrected so that the actual task number linked to each job is now displayed.

No notification was triggered when a job was issued with an engineer already assigned before the issue action. This has now been fixed so that the assigned engineer receives the new job notification when the job is issued.

Mobile job/quote creation failed when no cost code was provided and the system default cost code value was set to an empty string, resulting in a format exception during integer conversion.This has been addressed to ensure job/quote creation succeeds even when default cost code values are empty, with proper handling and resolution of cost codes across Service and Repair scenarios.

Some equipment collection notifications displayed unclear or incorrect titles that did not match the actual equipment collection activity, which caused confusion for users reviewing notification details. This has now been corrected so the notification title and details more accurately reflect the genuine equipment collection event, making the information clearer, easier to understand, and more reliable for customers and internal users.

Job sheets applied charge code rounding correctly to labour time but did not apply the same rounded value consistently to travel time, which caused travel to display differently even when the job had been submitted or completed. This has now been fixed so that working and travelling time both follow the configured rounding rules.

Some equipment remained incorrectly linked to terminated hire contracts even after being off-hired, which prevented users from adding the same equipment to a new contract because the system still treated it as associated with an existing contract. This has now been fixed so that once equipment is off-hired and the contract is completed and terminated, the association is cleared correctly, allowing the same equipment to be added again to new contracts.

We’ve removed email options from Jobsheet Pre Work communication rules to improve consistency across the Communication Center. This change ensures that email functionality and restrictions are applied more uniformly, helping simplify configuration and reduce confusion when managing communication settings.

We’ve fixed an issue where submitting a job could result in an error, particularly when attachments were included in the job work done notes. In some cases, this prevented the job from being submitted and the job details from loading correctly. This has now been resolved, and jobs with attachments can be submitted successfully without any errors.

We’ve fixed an issue where the Call Date and Target Date could display in different formats when a priority code was applied to a job. In some cases, the Call Date followed the user’s regional settings while the Target Date remained in a different format, which could lead to confusion. Both fields now consistently follow the correct regional date format, ensuring clearer and more reliable date display across the system.

An issue was causing the loading indicator to reappear after a job had already opened, which could interrupt the user experience and lead to users being removed from the job while working. This created confusion and made the job screen feel unreliable.This has now been resolved. Once a job has loaded, the loading indicator will no longer reappear unnecessarily, helping ensure a smoother and more stable experience when opening and working on jobs.

The “CFTS Thorough Examination Report V2” form was opening as a blank page for some users on both the mobile app and web, so the report could not be viewed or completed in the usual way.The form has been restored so that it now loads correctly on both mobile and web, allowing the report to be viewed and completed as normal.

When selecting a branch where no engineers are assigned to any team, the Select Engineer popup previously displayed a Team column and grouped all engineers under a “No Team” section. This added unnecessary complexity and required users to expand the group to view engineers.
​
This has now been corrected. If no engineers belong to a team, the list will be displayed in a simple flat format without a Team column or grouping. This provides a cleaner and more straightforward experience when selecting engineers in such scenarios.

Previously, the Revision History popup for Equipment Deal Quotations could show an incorrect status such as “Quotation” instead of the actual record status, which made it difficult for users to understand whether the record was still a quotation or had progressed to a deal. This has now been fixed so the popup shows the correct status based on the record type and state.

Searching for equipment records using keywords such as site or equipment ID could result in a persistent error, which prevented users from reliably finding equipment information. This has now been fixed so equipment searches complete correctly without showing the error, allowing users to search by relevant keywords and view results as expected.

Previously, the header checkbox remained selected even when sub-items were unchecked, causing inconsistent behavior. This has now been fixed to ensure proper synchronization between header and sub-item selections.

We’ve fixed an issue where cancelling the addition of stock parts in a draft quote could cause a “Task not found” error when attempting to add labour afterwards. In some cases, cancelling the parts selection would refresh the quote details and prevent further updates, which could also result in previously entered data being lost. This issue has now been resolved, allowing users to cancel part additions and continue adding labour without errors.

After triggering a validation message when selecting both a regular engineer and a subcontractor, the engineer list could become slow and unresponsive when the Subcontractor filter was toggled off and on again. This impacted usability and made it difficult to continue the selection process smoothly.
​This issue has now been resolved. The Subcontractor filter can be enabled or disabled without affecting performance, and the engineer list will load quickly and remain responsive even after validation messages are shown.

When selecting engineers during job creation, if a subcontractor was chosen alongside a regular engineer, the system correctly showed a validation message. However, after removing the subcontractor, the previously selected engineer was not recognised if the Subcontractor filter remained enabled, leading to an incorrect error asking users to add an engineer.
​This has now been resolved. After unselecting the subcontractor, the originally selected engineer will remain selected, and users can proceed without needing to adjust filters. This ensures a smoother and more reliable engineer selection process.

Priority was not being applied to service jobs created via ESS, even when a default priority was configured.Priority is now correctly included on jobs raised via ESS based on the default configuration.

We’ve improved the accuracy of the newly added last service date fields in the job data dictionary. These fields will now correctly display details from the most recently completed service for the same equipment. This ensures that users always see up-to-date service information, helping with better tracking and decision-making when managing equipment and jobs.

After accepting a sales order quotation, the global actions menu was showing an incorrect option and redirecting users to the wrong screen. Instead of guiding users to raise a sales order, the system displayed a “Raise Job” option and redirected to the job creation page.
​This has now been corrected. The global actions menu will display the appropriate “Raise Sales Order” option, and users will be directed to the correct sales order creation screen. This ensures a more accurate and intuitive workflow when progressing from quotation to sales order.

In some cases, job invoices could not be previewed from the job details screen when work‑done notes contained multiple images or large image files. Instead of opening the invoice preview, the screen displayed an error and blocked access to the invoice, even though the job itself was complete.The invoice preview process has been updated so that jobs with larger work‑done notes and images now generate the report correctly.

When selecting subcontractor engineers in the Select Engineer popup, task-related options were not fully hidden. Although the Task column was correctly not displayed, the “All Tasks” link could still appear after selecting a subcontractor, which created confusion as subcontractors do not support task-level assignment.
​This has now been resolved. Task-related options, including the “All Tasks” link, are completely hidden for subcontractor engineers. This ensures a clearer and more consistent experience, aligning the interface with how subcontractors are intended to be assigned.

MOBILE
​
Logging in to the mobile app using a code from the device‑registration process resulted in a server error, and the login did not complete. This blocked access for devices that had been correctly registered via the web.
​
The login flow for registered devices has been corrected so that codes generated during device registration now allow a successful mobile login instead of displaying an error.

Customer synchronisation could fail when an account name was longer than 50 characters, because that name was being reused in place of a contact name. This resulted in some customers and contacts not syncing correctly.
​The sync process now uses the dedicated contact details from Business Central rather than the account name for the contact field. This removes the length limit issue and allows customers and their contacts to sync as expected, even when account names are long.

When several journal items were posted together after fixing an invalid nominal code, only one item had its status updated. The other items still showed an error in the posting notes, even though they had been posted successfully.
​
The multiple‑item posting flow has been corrected so that all successfully posted items now have their status updated, and any old error messages in the posting notes are cleared once posting completes.

Expiry alerts were only being raised for stock items, while on‑demand parts that were close to expiring or already expired were not appearing in the Notifications tab. This meant expiring or expired on‑demand parts could be missed during everyday work.
​ Expiry alerts have now been updated to also include on‑demand parts. Notifications will be shown for on‑demand parts that are expiring soon or already expired, helping ensure all relevant parts are visible and important expiry dates are not overlooked.

​

​