Improvements

Inventory Audits: To prevent audit jobs from breaking, you can no longer change an Audit Type between Location or Item once an audit job has been created. If this field was incorrectly selected when the audit job was created, create a new job with the correct type.

Updates

Carriers: Updates carrier Parcll to reflect that they have renamed themselves to Cirro E-Commerce

Bug Fixes

Create/Edit Order: Resolved an issue when Replenishment is enabled for a warehouse where it wasn’t possible to manually allocate from non-pickable locations when using the Edit Allocation feature. Note that we will soon tighten down access to non-pickable locations to help prevent allocation mistakes when using Mass Add and Edit Allocations.

Manage Items: Resolved an issue when selecting a large number of items and clicking Export Selected where the system would throw a 404 error due to a data overflow.

Adjustments: Resolved a rarely occurring issue that resulted in the following error when trying to open the Adjustment module: "Not parseable: predicate must start with identifier", which was caused by the system not ignoring Reference Number values that consisted solely of spaces.

Locations: Resolved an issue when importing locations where null values in any of the “Locations" fields would cause an error when the system attempted to parse the file.

JSON Deserializer: Resolves a JSON deserializer error that could sometimes be encountered while running an end-of-day request.

SmartScan Receiving: Resolved an issue when scanning a GS1 barcode that contains a weight element (AI 3102) where the scanned weight displayed in the SmartScan UI but wasn't properly written to the database so it would show up in other areas of the WMS.

SmartScan Audit: Resolved an issue when scanning to add to the quantity being counted where each scan would add a digit to the quantity instead of just incrementing the existing quantity by one.

Audit Inventory: Resolved an issue when updating the Item History Size for an audit job where the grid did not automatically reload with the updated list of Suggested locations.

Audit Inventory UI: Resolved the following UI bugs in the new Audit Inventory page: The "Clear" button now clears all applied filters, including Warehouse; you can now select "Unspecified" in the "Assigned To" field; the "Job Includes Trackbys" filter works correctly now.

Replenishment: Resolved an issue when completing a move request with a partial quantity where the remaining quantity, which is assigned to a new move request, would be reduced by one. For example, if a move request for Qty 10 was completed by moving Qty 8, the new move request, for the remaining qty to fully replenish the pick location, would have qty 1 instead of the correct qty 2.

SmartScan: Resolved an issue when logging into SmartScan when Chrome or SOTISurf web browsers were unable to scan values into the Username and Password fields and you could not use <Enter> to advance from the Username to the Password field. Note that the proper behavior of the login screen when scanning requires the device to append <Enter> to the end of the scanned value.

REST API: Resolved an issue with the /receiverunconfirm endpoint where it would allow a receipt to be unconfirmed (re-opened) even though some of the receipt inventory had been allocated and shipped on one or more orders.

Manage Invoices: Resolved an issue when printing an invoice for an adjustment transaction where the invoice output would include a row for each defined adjustment-related charge instead of just those charges actually applied to the adjustment transaction. All charge calculations were correct, but the invoice included extraneous data that was not applicable to the selected transaction.

SmartScan Audit: Resolved an issue where scanning a SKU/UPC value with leading or trailing spaces would cause a 400 error in SmartScan. SmartScan now automatically strips leading and trailing spaces so the value scans properly.

Returns: Resolved an intermittent issue where the Return transaction creation date could be incorrectly set as the creation date for the user account being used to create the Return.