Bug Fixes - 25.1.20 - Released 26 August 2024

When dealing with a manufactured at POP item that is set to Pull (auto manufacture), the production order is created because of a back order on a sales order. When production is reported, the quantity to ship on the sales order line gets updated with that amount. This is normally awesome. However, in cases where the sales order processing gets ahead (or production order reporting is behind), the sales order could already be in process. Updating it at this time can cause all kinds of problems. As a result, we updated the report production process to ignore updating the sales order line if the sales order status is at confirm ship or later.

This initially seemed to be an issue with the selection ShippingEasy connector, but it turned out the actual problem was that the order(s) being sent to ShippingEasy was on-hold. This fixes the ShippingEasy upload so that on-hold orders are not sent up.

Macola Progression has a unique index on ARCshApl_sql.tm_stamp and that field only has seconds precision. This means that when using BirdDog tools like the Cash Receipts Integrator, we could get duplicate key exceptions when creating more than one entry per second - for example, if you had a $1500 invoice and you received fifteen payments of $150 apiece but were, inexplicably, using the same check or voucher number (which, admittedly, is an edge case). This fixes that issue and allows the system to handle this more gracefully.

Shopify only supports APIs for a year, so as of this build, we updated the BirdDog Connector Sub-System for Shopify to use the Shopify API 2024-07. In the course of this, we also had to do some connector label clarification as it appears Shopify changed a few minor things.

Fixed some tooltips on Order Edit.

When using the 1 EDI Source connector and a file with a PO that already existed was uploaded, the system was logging that there was a duplicate PO when connectors was run ... every. Single. Time. We've changed that functionality to log the duplicate error once, and then delete said duplicate file from the system.

Improved Infor Syteline connector order mapping; if an order is on-hold in BirdDog due to exceeding the customer's credit limit, that order will be uploaded to Syteline with a status of Planned.

The Assigned To column on the BRAIN Matter table of the Incident Form needed a width set to it.

Orders generated with an auto-manufactured item were showing the work order number on the Order View under Rep Ord No, but it was no longer a hyperlink to that work order. Now it's back to normal.