Bug Fixes: Version 9.9.0.97 - Released 30 August 2019

×
This build has the following bug fixes implemented: 
Fixed
10670569 - Customer Upload Query in Connectors doesn't handle Macola ES
Coding fix to resolve an issue specific to Macola ES when using the BirdDog Connector Sub-System.
Fixed
10780931 - Could Not Get Shopify Id for Item #PROMO
Bad data was preventing the BirdDog Connector Sub-System to choke when trying to download orders when specific parameters were met.
Better
10803277 - Location Description Needs to Longer for M1
The M1 system allowed for a much longer description for locations than previously expected, so attempts to download data from it via the BirdDog Connector Sub-System caused errors.
Fixed
10825989 - Custom Pricing and Description Not Updating Line Items from Sage to SP
When setting up custom pricing in the Sage 100 ERP system and using the BirdDog Connector Sub-System to sync up to Service Pro, this pricing was not being pushed up at all.
Better
10826048 - Run Connectors on Initial M1 Process Requires GL Account
A blank BDEngine database hit by the BirdDog Connector Sub-System for M1 for the first time prompted the creation of a new GL account to be used as default. No reference existed to this GL account in Maintain Connectors or exactly what this GL account was for.
Better
10835995 - Location in Sage 100 Can Have Blank Name, Description, and Address
In the Sage 100 ERP, certain features that BirdDog expects to be populated can be left blank; as a result, when using the BirdDog Connector Sub-System to upload this information, an error was stopping the process dead in its tracks. Now the system handles this much more gracefully.
Fixed
10836638 - Customer is Uploading to Shopify but No Info is Going Other Than Name
Using the BirdDog Connector Sub-System for Shopify and uploading a customer using query as the method for deciding which customers to upload, the only info that was being uploaded was the customer's name. There is no address or email address or any of that information being uploaded with the customer.
Better
10837968 - Location, SalesPerson and Tax Code Errors in Sage 100 Connector
Similar to 10835995 above, in the Sage 100 ERP, certain features that BirdDog expects to be populated can be left blank; as a result, when using the BirdDog Connector Sub-System to upload this information, an error was stopping the process dead in its tracks. Now the system handles these much more gracefully.
Better
10839888 - Sales Person on Magento Connector Requiring Max Length of 3 on ES Database
When using the BirdDog Connector Sub-System to connect Magento and Macola ES, the system was not handling differing lengths for the Salesperson code correctly.
Better
10841391 - Duplicate Key Exception Writing Price Codes
When using the BirdDog Connector Sub-System with a M1 system, the connector was erroneously reporting this exception while writing price codes.
Fixed
10850339 - M1 Connector Didn't Bring Over Default Location
When setting up an item in M1, you can assign a "default bin". This now corresponds to our default location. Previously, an item that had multiple locations with location 01 was marked as the default could be downloaded with another location erroneously marked as the default.
Fixed
10912001 - Bill_To_State too long (Max length=3), value: TH-10
Larger than expected bill to state codes - in this example, Thailand - were not being handled correctly when coming down from Shopify via the BirdDog Connector Sub-System.
Better
10914150 - ALTER TABLE ALTER COLUMN Cus_No Failed Because One or More Objects Access This Column.
Coding fix to handle bad data when using the BirdDog Connector Sub-System to sync Service Pro with the Sage 100 ERP.
Better
10924592 - Ship To Name not passing from Service Pro to Sage 100
When using the BirdDog Connector Sub-System, the address set on a sales order in Service Pro was coming down to Sage 100, but the Ship To name was not correctly passing on.
Better
10934495 - Misc Item /Shop Not Allowing Quantity to Write Into Sage From Service Pro Order
When using the BirdDog Connector Sub-System to sync Service Pro and the Sage 100 ERP, Miscellaneous Items from Sage were not being handled properly as they do not have an actual location in that system but are expected to for Service Pro.
Fixed
10934649 - Kits Not Functioning Properly in Sage/SP Connection.
Orders generated in Service Pro and downloaded to Sage 100 via the BirdDog Connector Sub-System were not populating kit items correctly in the latter.
Fixed
10936541 - Input String Was Not in a Correct Format
When using the Sage 100 to Service Pro connector, certain orders were not downloading correctly due to this error.
Better
10938093 - Only Inventory Option of SvcPro Misc Item Integration Pushes to SvcPro
In the Sage 100 ERP, Miscellaneous Items have several sub-categories. Only the Inventory sub-category was correctly being synced up to Service Pro when using the BirdDog Connector Sub-System.
Fixed
10941107 - Incorrect Syntax During Upload to Service Pro
Coding fix to handle bad data when using BirdDog Connector Sub-System against Service Pro.
Fixed
10978954 - Getting 'Request does not match any route' When Uploading CusNo via Query
Coding fix to resolve an error for bad data when using the BirdDog Connector Sub-System against Magento.
Fixed
10983239 - GL Accts Not Populating on Maintain Connector Due to Item Broken Rules
Unexpected GL structure from Sage 100 was causing the BirdDog Connector Sub-System to fail when trying to sync these accounts up to Service Pro.
Fixed
10983403 - String or Binary Data Would be Truncated Error
When using the BirdDog Connector Sub-System with a M1 system for the first time, this error was being generated and preventing forward progress.
Fixed
10993514 - Second Item Line on SvcPro Order Not Bringing Down Custom Pricing
Orders created in ServicePro with multiple lines and custom pricing that were downloaded into the Sage 100 ERP via BirdDog Connector Sub-System were not bringing down the custom pricing for the second line item. Just that line item, though; the others were fine.
Fixed
10998206 - SvcPro Order Comments Not Coming Down to Macola
Orders generated in Service Pro that have line or order comments and were being synced down to Macola via the BirdDog Connector Sub-System now correctly bring those comments down as well as the other expected information.
Fixed
11013394 - Shopify Connector Tries to Download Orders Lower Than the "Starting Shopify Order#" Field is Set to
In the Maintain Account portion of the BirdDog Connector Sub-System for Shopify, you can set the Starting Shopify Order ID. The system will ignore all orders before this number, but was previously still trying to download them.
Fixed
11014220 - Cannot Insert Duplicate Key Row in Object 'dbo.BDConnectorLinkages' with Unique Index 'idxBDConnectorLinkagesConnectorIDTypeLocalIDLocalID2LocalID3LocalID4LocalID5'
Fixed logic issue causing duplicate index
Fixed
11015464 - Get Error After Order Fulfilled in Shopify
Using the BirdDog Connector Sub-System for Shopify, an error was being generated each time a new order was fulfilled that prevented the connector from successfully running again until this error was fixed.
Better
11025590 - Issues with Prospect Quotes
Prospect Quotes are an unsupported order type for the BirdDog Connector Sub-System for Sage 100, but they were still being picked up which was causing errors.
Better
11027763 - Don't Send Order to Service Pro Unless All Items Have a Linkage
If an order generated in the Sage 100 ERP has items that have not had their Service Pro type set, the BirdDog Connector Sub-System will report a warning that this line item need to have its Service Pro type set.
Better
11036899 - Phantom Linkages Aren't Being Deleted
When using the BirdDog Connector Sub-System, deleting a line on a sales order deleted the line, but the linkage record never got deleted as well which was causing issues with that order if it was later edited again.
Better
11037623 - Need To Truncate Item Descriptions Coming From SP To Macola
Service Pro accepts significantly larger item descriptions than Macola so, when downloading items from the former into the latter using the BirdDog Connector Sub-System, the system automatically truncates these descriptions to fit Macola standards.
Better
11045199 - Connector is Trying to Pull Down Cancelled Orders from Magento
The BirdDog Connector Sub-System no longer attempts to download cancelled orders from Magento.
Fixed
11074812 - Discounts in Shopify Order are Ignored on Macola Order
Orders generated in Shopify and downloaded to Macola via the BirdDog Connector Sub-System were ignoring discounts and re-calculating prices.
Fixed
11098758 - Sage Order Date Does Not Match the ServicePro Order Date on Orders Created in ServicePro
Orders created in ServicePro and downloaded into the Sage 100 ERP via BirdDog Connector Sub-System were writing a date that is actually older than the real created date.
Fixed
11129733 - Increasing the Version Number of an Inspection Breaks the Integration
Items in ServicePro that have been adjusted to be a new version were not downloading correctly via BirdDog Connector Sub-System even though the item number itself was not changing.
Fixed
11135226 - JobMaster Treating No Logging Level in Birddog.config as Logging Level 0
If the config file did not have a logging level, Job Master wasn't logging anything at all, which made troubleshooting issues difficult to say the least. Now, if no logging level is set, Job Master will report that in the presumption that you'll fix it so it can properly log errors.
Better
11135789 - Ignore Duplicate Databases in the Config File
Now that Job Master also reads the same config file that we use for the website, there existed the possibility that a Job Master instance could have two different config files in the same folder. If those two config files had the same database, some jobs could run twice against the same database at the same time, thus stepping on one another. Now, if the system detects two config files with the same database information, it ignores the duplicate entirely.
Fixed
11158188 - Content-Type Header is Empty Error when Uploading Customer to Magento
Some customers did not sync down from Magento properly when using the BirdDog Connector Sub-System.
Better
11165205 - Order Line Broken Rules Don't Give the Detail of the Error
Improved logging for certain orders to better facilitate troubleshooting.
Better
11282286 - Tax Code Being Set When It Should be Tax Schedule
In rare instances, Service Pro was allowing an order to have both Tax Codes and Tax Schedules on the same order, which is illegal in most systems. Now, when using the BirdDog Connector Sub-System to download such an order, the tax code is ignored in lieu of the tax schedule.

Receive your free product tour!

Need Help? Have Questions?

Industries

Find out how BirdDog Enterprise fits your niche!