Barcoding & Warehousing

Back to release notes

220.0.1

New Features Hot Fix Enhancements
New Features

Added setting for disabling the prompt for package dimensions when despatching an order.
Added a drop down for a courier label printer to be set to a user.
Prompt user to select component warehouse during WOP Backflush if ‘Use Sage SOP Stock Fulfilment Sequence’ is configured.


Hot Fix Enhancements

Improve error reporting if SOP despatch coordinator fails to set quantity, for example if insufficient stock is allocated.
Fix ‘Sequence contains no elements’ if nothing to despatch due to kit build failure.
Don’t attempt to create despatch notifications, print despatch notes or SOP invoices if no items despatched.
Fix ‘object reference is not set …’ error in GetKitLinesToDespatch() if pre-allocations have been deleted.
Fix SOP Despatch box/quantity corruption if picking into bags & then packing into boxes resulting in item quantity being split between separate pick/pack boxes.
Fixes purchase orders ignoring the buying unit set in the PO line when receiving via a container.
Fix bug that displayed the stock item base unit instead of the buying unit set in the PO line on the receive container list.
Fixed UI values not being properly displayed when deleting bins within Sage.
Fix for ‘an item with the same key has already been added’ message when despatching kit lines from 2 separate packages.
Fix Receive Purchase Order hand held device error ‘The null value cannot be assigned to a member with type System.Boolean which is a non-nullable value type. (Server 500)’ error (due to SiconWABStockItem boolean fields set NULL).
Dynamic Stocktake new method added to read traceable attributes for an existing batch/serial + set attributes & use/sell by dates passed from device when adding traceable stock.
Photos taken in the Sales order processing screen, are now being properly uploaded to Sage.

DespatchSOPLines Web API log informational messages added.


Date applied: June 8, 2022