Bug Fixes: Version 9.9.4.30 - 3 March 2020

×
This build has the following bug fixes implemented: 
Fixed
11419187 - Synergy Database has Wrong Collation Type
Some Synergy databases had a different colation from the Macola ES database which kept customers from being added.
Better
11484348 - Update Invalid ServicePro Work Order Line Data to Warning
Changed an error alert to a warning.
Fixed
11494078 - Sage Using Older Date Sometimes in Order Creation
When bringing down orders into a Sage 100 environment using the BirdDog Connector Sub-System, in specific scenarios, the order date was being recorded incorrectly.
Better
11512856 - Only First Price Code Uploading from M1
Only the first price code was uploading properly when using the BirdDog Connector Sub-System against an M1 environment and had an actual discount/markup/price. All others uploaded but have those fields blank.
Better
11567995 - Items Downloading Every Time
When using the BirdDog Connector Sub-System against an M1 environment, items were being pulled down every single time the connector was being run, but it was not reporting them. As a result, the run connector process was taking an extremely long time to complete.
Fixed
11593198 - Invalid column name 'ID'. Invalid column name 'RowVersion'. Invalid column name 'CreatedTime'. Invalid column name 'LastUpdatedTime'. Invalid column name 'CreatedByID'.
Some incorrect assumptions were made regarding revcode logic which was causing this ugly fail when using the BirdDog Connector Sub-System against Service Pro and Sage 100 environments.
Fixed
11779984 - Orderline Inserted Between Existing Orderlines in Sage Causes Error When Syncing
Inserting an order line between two existing order lines in a Sage order caused a "Cannot insert duplicate key row" error when syncing the order to Service Pro through the BirdDog Connector Sub-System.
Fixed
11783059 - Sage Customer Columns Are Not Always in the Same Order
The underlying tech that was used to pull data from Sage 100 using the BirdDog Connector Sub-System was column order specific. This was based on the assumption that every Sage install had the table columns in the same order which turned out to be an invalid assumption. This bug fix switched it to use column names instead of the column index.