Skip to content
English
Customer Portal
Contact us
  • There are no suggestions because the search field is empty.

Release Notes v2 2.3

Version V2-2.3

Detailed Fix Summary

This release focuses heavily on stability corrections, accounting clarity, and improved API reliability.

Material Screen Crash (UOM = Null)

Issue

Certain tickets or materials with a missing Unit of Measure (UOM) caused an object reference error. This resulted in the following behaviors:

  • Crashes when opening the Material tab
  • iPad login issues in rare cases
  • Errors when loading specific customer or ticket data

Fix Implemented

  • Added null-check handling in code to prevent crashes.
  • Improved validation to prevent incomplete material records from causing runtime failures.
  • Ensured the system safely handles legacy data where UOM may not have been defined.

Result

Material screens now load reliably even if historical records contain missing values.

Accounting Transaction Screen Improvements

Issue 1: Sage Transactions Not Displaying

Issue

Sage transactions were not appearing consistently in the system.

Fix Implemented

  • Reworked how Sage entries are stored and displayed.
  • Moved Sage entries to the unified Accounting Transactions page (same structure as QuickBooks/QBO).
  • Removed duplication from Upload History.

Result

All accounting integrations (Sage, QBO, QuickBooks) now follow a consistent display model.

Issue 2: QBO "No Data" Confusion

Issue

When QuickBooks Online returned no transactions due to settings, the screen appeared blank.

Fix Implemented

  • Added a clear informational message when no data is returned.
  • Eliminated confusion between "no data" and "system error."

Result

Users can now easily determine when there is simply nothing to sync.

Inventory Workstation Camera Setup

Issue

Inventory workstation configuration performed duplicate camera validation checks.

Fix Implemented

  • Removed redundant validation logic.
  • Simplified workstation setup workflow.

Result

Cleaner setup process and reduced configuration errors.

SR App API Corrections and Enhancements

Issue 1: Cash Rounding Not Properly Reflected

Fix Implemented

  • Added RoundingAmount and RoundingType to SR App Login API.
  • Ensured rounding prints correctly on tickets when enabled.

Issue 2: "Do Not Buy" Flag Not Passed Correctly

Fix Implemented

  • Added DoNotBuy parameter to the CreateCustomer API.
  • Added DoNotBuy parameter to the GetTicketByTicketId API.

Result

The mobile app now respects customer purchase restrictions consistently.

Issue 3: Image Existence Detection

Issue

The mobile app could not reliably determine whether certain customer or ticket images already existed.

Fix Implemented

Added image existence flags to APIs for the following image types:

  • Customer license
  • Signature
  • Thumbprint
  • Customer photo
  • Vehicle image

Result

Improved mobile performance and reduced unnecessary image downloads.