New Features

Using the BirdDog Connector Sub-System: added setting which allows log entries to be posted up to Service Pro; added a setting to the Service Pro connector which allows you to set the logging level of entries that get pushed up to Service Pro's logs from BirdDog's logs.

In Macola ES, the "Rates" table needed to be added to the sync process.

In previous versions of the BirdDog Connector Sub-System against Sage 100, generating a customer needed to happen entirely on the Sage 100 side; with this build, you can now create them in BirdDog applications such as Ecommerce or Customer Service or our third part connectors that support creating customers such as Shopify, Woo Commerce, Magento, and Service Pro and they will sync down correctly to Sage.

The "Process On Hold Orders" job was throwing an error because the query had the page code in it and it was looking for the webcategoryID guid; we revised this to look for both.

The BirdDog Connector Sub-System was erroneously trying to write information from Service Pro into a specifc table that is not actually tracked or used anywhere.

Due to some coding from previous versions, we were continually logging orders that were not marked to send to Service Pro using the BirdDog Connector Sub-System when the process ran. This led to some confusion as some users thought it meant there was a problem; to clear up the confusion, we no longer put that warning in the report.

When using the BirdDog Connector Sub-System, after generating a new customer Ship-To in Sage 100, this Ship-To was not uploading to Service Pro like it should.

While setting up the Magento Connector Sub-System, clicking on save was causing several of the dropdown lists to revert to data options that you had not actually selected.

Added exception handling to keep upload customers and ship tos from stopping the process when using BirdDog Connector Sub-System against a Sage 100 environment.

Similar to 11710708 above. Added exception handling to keep sales orders from stopping the process when using BirdDog Connector Sub-System against a Sage 100 environment.

An order generated in Service Pro using a newly created customer with some sketchy data was causing the Sage Connector Sub-System to throw an ugly error.