Bug Fixes - Version 12.1.68 - Released 28 July 2021

Attempting to Checkout using a credit card that has more than 40 characters in the customer name threw a site error.

In v13.0, we add a unique index to BDCarts.OrdNo. This change requires that OrdNo be NULL when not set. We are making this update here to make 12.1 schema compatible with v13.0.

When entering a Credit Memo in Macola ES and sending it to Avalara using the AvaTax connector for tax calculation, we received a negative number back from Avalara for the Tax Amount. The connector was writing that negative Tax Amount to the Credit Memo, which resulted in the Tax Amount being subtracted from the Order Total on the Credit Memo.

The site settings onscreen help for Ecommerce | Checkout | Freight Pay Methods was erroneously referring to Customer Service data, not Ecommerce.

Clicking on System Menu | Admin | Sales Report and attempting to Generate a report caused a hard software crash referring to a DLL that was newer than the one in BD Ca$h.

When you changed quantity to zero for an item in BD Ca$h, the item was removed but any tax that had been determined was not also zeroed out.

There was a formatting issue in the query to get the next entry number that caused journal numbers that were less than 3 characters long (ie. 90) to return an incorrect entry number, which would sometimes cause a duplicate key exception.

Dollar values on the print sales report from BD Ca$h were incorrect and the report showed a higher total than actual sales.

When setting an order date on an order created in Sage 100 to something earlier than the current date, that date was getting overwritten to the current date by Service Pro when the order was synced up. That current date was then synced back down to Sage, overwritting the date set on the order in Sage.

An order with a new customer generated on a synced Macola 10 site was not syncing down to local and software was throwing this error. Both have been resolved.

The Enterprise for Windows command line call to authorize a credit card assumed it was given a range of orders and did not handle a single order gracefully.

If the customer currency is changed to something other than USD ($), the freight rating dropdown list was still showing $ instead of the new currency symbol.

When sending a credit card transaction to Authorize.net that contains more than 30 lines items, we received a CC declined error.

When new users/customers were created on the website, the cus_no of an existing customer was being attached to another users session, resulting in the second user getting attached to the first user's customer number.