Skip to main content

Release Notes 17 September 2025

Release Notes 6.85.39

J
Written by Jui Hande
Updated this week

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

Enhancements (5):

New Field Added to Hire Agreement dataset

A new field, Equipment Power, has been added to the Hire Agreement dataset. This provides additional context for each activity and supports more detailed reporting.

Incorrect Total Purchase Value on Empty Purchase Orders

The “Total Purchase Value” still displayed figures even after all line items were removed from a purchase order. The system now correctly recalculates totals and sets the PO status to “Draft” when the last item is removed.

New Field Added to Engineer Activity Dataset

A new field, Reason, has been added to the Engineer Activity dataset. This provides additional context for each activity, supporting better reporting and analysis.

Editable PI VAT for Supplier Invoice Matching

Previously, users could not edit VAT at the line level, leading to discrepancies between SG and supplier invoices due to rounding differences. The PI value for goods and VAT is now editable, allowing users to match supplier invoices more accurately. This reduces manual corrections in Sage and improves invoice integrity.

Faster Job Completion by Optimizing Form Processing

We’ve improved the speed of job completion by streamlining how the system processes forms attached to a job.

Mobile Update

A New version of the Mobile App has been released, release notes for this can be found here: Mobile Release Notes

Fixes (9):

SKU Quantity Filter Now Works for Zero Stock Items

Filtering SKUs by a quantity of zero did not return the correct results when raising a purchase order. The filter now works as expected, allowing users to accurately identify items with no stock.

Purchase Order Notification View Now Ignores Saved Filters

Clicking “View” from a PO approval notification didn’t show the relevant PO if a saved filter was applied in the PO enquiry screen. This has been fixed, notifications now open the correct PO regardless of saved filters.

Closed Purchase Orders Pagination Issue Resolved

Fixed a bug where navigating through pages in the Purchase Order enquiry screen failed to display closed POs correctly. Previously, selecting “Show All Closed Purchase Orders” would show a total count, but moving to the next page resulted in no data being shown. This issue has now been resolved, and users can view all closed POs across multiple pages as expected.

Error When Viewing On-Order Quantity in Part Requests

Clicking on the “On Order Quantity” in the Part Request screen caused an error. Users can now view purchase order details without any issues, across both “All Depots” and “Specific Depot” views.

Invoice Schedule Protection for PM Contracts

Changing the invoice start date or frequency after invoicing had begun could cause missing invoice schedules. The system now prevents changes to recurring invoice settings once invoicing has started, ensuring consistency and avoiding disruption to scheduled invoices

Job History Loading Issue Resolved

Addressed a problem where job details failed to load when accessed through the equipment history view in the Service Call screen. Users can now open job details without delay or loading issues.

Mobile Job Completion Reliability Improved

Resolved an issue where some job completion messages from the mobile app were failing to process correctly. The system now handles job completions more reliably, ensuring that all submitted jobs are recorded as expected.

Purchase Order Cancellation Issue Fixed

Resolved an issue where users were unable to cancel a purchase order (PO) linked to a job. Previously, the PO could only be cancelled after manually deleting its line items. This has now been fixed, and users can cancel POs directly without extra steps.

Job Opening Issue Resolved

Fixed a problem where some jobs couldn’t be opened due to missing pricing information. This caused an error message to appear and blocked access to the job. The issue has been resolved, and jobs will now open as expected.



Did this answer your question?