Bug Fixes - Version 13.0.27 - Released 28 July 2021

×
This build has the following bug fixes implemented: 
Better
11835692 - Connector Greatest Seen Time Intermittently Reverts Back Far in the Past
The greatest seen time login in the Connector Sub System had an assumption that it would never be given a date older than one it had already seen. This assumption was being broken by some of the connectors causing the system to re-process data.
Better
11836635 - Update Service Pro Connector to Round Trip Unit Price and Sales Tax Changes
Prior to this build, you could set the Service Pro Sync Order Line Unit Price on the Connector Sub-System for Service Pro. However, if this was unchecked, even though we updated the price correctly in the BirdDog database, we were not pushing the change back up to ServicePro itself. Further, if using the Service Pro connector while licensed for Avalara, we now push the calculated AvaTax amount back up to Service Pro.
Fixed
11836696 - Carts Table Missing Unique Index
Fixed issue with the Carts table that allowed multiple carts with the same order number.
Fixed
11837535 - Improve Error Message When Sage 100 Can't Set The Task
Continued improvements to the Sage 100 connector error messages when Sage 100 is having technical issues
Fixed
11837578 - Item Weights Not Coming In From M1
Added Lead Time, Weight, Weight UOM, and Country Of Origin to the Item download for the M1 connector sub-system.
Fixed
11837741 - Tax Code Percentages Coming In Wrong to Service Pro
Sales Tax Codes brought into Service Pro using the Connector Sub-System are coming in with the decimal points in the wrong place; a 7.75% code is coming into SvcPro as .0775.
Fixed
11838089 - Sequence Contains No Elements Error When Running Service Pro Connector vs Macola
Running Service Pro connector against a Macola Progression database threw the above error which never went away when dealing with unexpected data.
Fixed
11838186 - M1 Connector Doesn't Handle Items Without a Description
When running a connector sub-system pointed to the M1 ERP, items without a description and items that ended in a non-breaking space were causing errors without giving a proper explanation. We updated the connector to properly handle both scenarios.
Fixed
11838265 - Freight Pay Code Other Than C Not Recognized As Collect
Using Ecommerce, when a freight code was set up as Collect but the code used was not C, the system was failing to properly recognize that it was actually Collect and never showed the appropriate dropdown list and fields for setting collect freight information during checkout.
Fixed
11838455 - Service Pro Connector Pulls Salesperson from Customer Record Instead of Order Header
When syncing an order from BirdDog to Service Pro, the Salesperson field is being pulled from the Salesperson on the Customer Record, instead of Salesperson from the Order Header.
Fixed
11838460 - Object Reference Error on Enterprise for Windows Import Sales Orders From Directory
Going to Enterprise for Windows | Utilities | Integrate | Sales Orders from Directory threw an error when clicking on it in the menu.
Fixed
11838817 - Item Copy Sets Activity Date And Location Quantities Incorrectly
When copying an item in Enterprise, the new item was incorrectly showing the old items activity date, quantity on hand, quantity allocated, and quantity on order.
Better
11839543 - Item Import Updates Records That Haven't Changed
When doing an import of records through Enterprise for Windows | Utilities | Import that contains both changed records and records that haven't been changed since the last import was done of that data, the connector was processing and uploading the unchanged records to Service Pro, resulting in a connector run that took a long time to complete.
Fixed
11839601 - Error setting property EMAILADDRESS$ When Downloading an Order With No Email Set On Sage Customer
There were two issues that this build resolved for the Sage 100 connector: When a sales order didn't have a related cart, the default ordered by email address was defaulting incorrectly; and if the sales order ordered by email address was invalid, it errored out the entire order, now it just reports a warning.
Fixed
11839635 - Sage Connector Not Pulling Constituent Tax Codes In Tax Schedule
When creating and downloading a tax schedule from Sage 100 to BirdDog via the connector sub-system, the tax schedule was being downloaded, but the tax codes that make up that tax schedule weren't.

Receive your free product tour! Need Help? Have Questions?

Industries

Find out how BirdDog Enterprise fits your niche!