Bug Fixes - 20.1.49 - Released 30 November 2023

×
This build has the following bug fixes implemented: 
Fixed
11833973 - Capture Credit Card Resets Sales Tax To Zero Using AvaTax If The Employee Doesn't Have Item Permissions
This was encountered when a User had the Employee role and was attempting to invoice items using Enterprise for Windows that the Employee role did not have view permissions for. The lack of proper permissions there caused the item to not load correctly and a null item get handed back where the taxable default was set to false. As a result, AvaTax zeroed out any tax.
Fixed
11857185 - JobMaster Not Honoring ApplyDatabaseRevision Setting in Config
In the Job Master config file, adding " " should prevent it from performing schema updates for new versions of the software if Job Master is the first program to run a new version against an existing database. The code was not honoring that setting.
Fixed
11858281 - M1 Salesperson Mapping Incorrectly
Using the M1 connector sub-system, we were mapping BirdDog Salesperson to M1 AccountManager (Organizations.cmoAccountManagerEmployeeID), and it was supposed to be OrganizationLocationSalesPeople. This also removes the mapping of customer.salesperson to organization.cmoAccountManagerEmployeeID. Customer.salesperson is mapped to OrganizationSalesPersons.cmkSalesEmployeeID.
Fixed
11860475 - Shipping Interface Requires Item Permissions
Related to 11833973 above, although with slight differences that are only immediately apparent under the hood. Shipping Interface can select orders for billing. In a scenario where you have the AvaTax connector, the system must load the item to determine tax settings. Previously, if you didn't have the correct item permissions, the system could miscalculate sales tax. If you have permission to run the shipping interface command, it does not matter what your item permissions are.
Fixed
11862408 - Sales Order With Duplicate Tax Codes Won't Post
Attempting to post an order set up in this fashion was resulting in a duplicate key exception error instead of posting.
Better
11862429 - Fix Invalid Ship Code Error
Improved a bad error message for when site settings have invalid ship via code data.
Fixed
11864065 - Shopify Connector Order From Remote System Not Working
When using the 'Order from Remote System' option under 'Order Number' settings on the Shopify connector sub-system, it did not behave as expected.
Better
11865108 - Make Payment Page Looks Odd When Browser Is Fullscreen
Several of the built-in buttons on the page weren't in the right place when the web browser was set to fullscreen.
Better
11865537 - Change M1 PartWarehouseLocations Errors to Warnings
When downloading data from the M1 table PartWarehouseLocations, we were reporting errors when we ran into invalid data. This caused the connector not to finish successfully. Changed those errors to report as warnings.
Fixed
11865584 - Sage Connector Not Retrying Orderline Upload After Receiving a Record Lock Error on Order in Sage
When attempting to upload new orderlines to Sage 100, if we get a "Record Lock" error because the order is open in Sage Sales Order Entry (or for whatever other reason), we throw a warning in logging, but never attempted to re-upload those orderlines to Sage. Bumping the order or making a change to it would cause it to be reprocessed, but the missing lines never synced to Sage.
Better
11866167 - Field Maintenance Screen Needs Tweaks
Made a number of minor UI improvements: changed the existing mouse-over tooltips to match our standard; changed the label on one option to be more clear; fixed a couple of minor typos; added a link to another page on one the tooltips.
Better
11866168 - Page Title on UOMList is Wrong
The page title for UOM List was showing Freight Cost List instead of Units of Measure.
Fixed
11866265 - Work Order Screen Not Displaying The Item Description
When displaying work orders at Enterprise | Manufacturing Work Orders, the screen crashed because there was an issue with the Item Description.
Fixed
11867055 - Sage 100 External ERP Type isn't being set
When the connector is initially run against a new database, it sets which external ERP will be utilized based on what is set in the initial connector setup. This is important as the schema is frequently different according to which ERP is involved - for example, one ERP may have a character limit of 8 for customer numbers, but another may allow 16, and so on. An earlier version of the software introduced a regression bug that was preventing this value from being set for Sage 100 and, as a result, the schema was not being updated correctly.
Better
11867752 - Order Header Doesn't Handle Invalid NULLs Gracefully
Observed with an order that was created illegally with NULLs in fields that should never be NULL. This update makes the system no longer crash when it encounters such data in the wild.
Fixed
11868457 - Reprint Invoices from EntWin is Erroring Out
When using Enterprise for Windows and navigating to Transactions | Invoicing | Reprint Posted Invoices, the system was throwing an error stating "Column 'email_address' does not allow nulls."