Version 13

×

13.0

System Requirements Version 13


13.0

Bug Fixes - Version 13.0.36 - Released 15 September 2021

This build has the following bug fixes implemented:
Fixed
11836227 - Billed Date Not Being Handled Correctly
This resolves two similar but slightly different issues: when using Macola Progression, the Billed Date was not being set to today's date when the order was selected for billing, and when using Macola ES, the Order Date Billed was not being cleared on a backorder when a shipment was posted.
Fixed
11837737 - Item Request Date Not Matching Order Date
By default, our system automatically sets a new order's "request date" to the "order date"; we weren't doing that in newer builds.
Fixed
11840791 - Sage Miscellaneous Items Not Uploading to SvcPro
A miscellaneous Item created in Sage 100 appeared to come into the BirdDog DB correctly, and logging showed it being uploaded to Service Pro, but the item never actually appeared in SP, and the SP linkage for the item got a RemoteID of "unassigned-/ITEM_NO" and a RemoteID 2 of "Unassigned". No errors or anything in logging were being recorded beyond the "Uploaded /ITEM_NO" entry.
Fixed
11840950 - Invalid Contact Created When Emailing from Customer Service
When emailing a quote/invoice from Customer Service using a list of multiple destination email addresses, instead of creating a new task and attaching it to the existing contact associated with that email address (or creating a new contact if it doesn't exist), the system created a new contact that has the entire list of email addresses as the contact username.

Back to Top

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.

Back to Top

New Features

This branch has the following features implemented: 
New
11641730 - Epicor Connector
This enhancement updates the BirdDog Connector Sub-System to integrate the Epicor ERP with our ecommerce platform. This is currently a level one integration in that we download items, customers and all of the connected data required to ensure those function from Epicor to BirdDog, and uploade sales orders from Ecommerce back to Epicor. Coordinate with BirdDog to set up this connector.
Better
11836635 - Update ServicePro Connector to Round Trip Unit Price and Sales Tax Changes
Prior to this build, you could set the ServicePro connector sub-system to "Sync Order Line Unit Price." However, if this was unchecked, even though we updated the price correctly in BirdDog, we didn't push this change back up to ServicePro. In addition to fixing that, with this build, if you are using the ServicePro connector and are licensed for AvaTax, then the connector will push the calculated AvaTax amount up to ServicePro.
Better
11837192 - CertCapture Connector Shouldn't Require the Verified Flag To Be Set on a Cert to Download
We made a number of improvements to the Avalara CertCapture connector functionality:
  • Cert no longer has to be verified to download.
  • Reporting of duplicate certs as a warning.
  • Overwrite cert if a newer expiration date is found.
  • Sales Tax certs downloaded now show on the connector report.
  • Cert download updated to use the greatest seen time sub-system so it won't try downloading all certs on every run.
Better
11837578 - Item Weights Not Coming In From M1
Previously, we did not bring item weights into Ecommerce from M1 via the Connector Sub-System, which limited freight rating functionality. As of this build, that has been added to the system.
Better
11837866 - Weight UOM is 3 Chars in M1 But Only 2 Chars In BD
M1 allows 3 character UOM fields but we only supported 2 characters. This build extended it to 3.

Back to Top

Upgrade Notes

Due to 11836696, customers already running Ecommerce or Customer Service need to have all versions of BirdDog Software that will run side by side with 13.0 brought to 12.1.49 or later before deploying 13.0 or later. Earlier versions of the code will experience exceptions saving carts after 13.0 or later has updated the schema. Note that this is only for Ecommerce sites that have multiple websites pointed at the same database (for example, a www.yoursite.com and estaging.yoursite.com scenario.) Connector systems do not need to worry about this.

Back to Top

Reason for Point Release

This point increase (v12 to v13) was caused by the integration of the connector sub-system for the Epicor ERP. This is basically a point release for 12.

Back to Top


System Requirements Version 13

Server Requirements

Software Requirements
BirdDog Software can be deployed on a dedicated or virtual server that meets the following requirements:

Minimum hardware required:
  • Windows 2008 R2 Server
  • Minimum: 8 GB of RAM, recommended: 16 GB of RAM
  • Minimum .Net Framework 4.7.2
  • 300-500 MB of available hard disk space per installed instance of BirdDog
BirdDog software can be installed on both x86 (32-bit) and x64 (64-bit) versions of the following:
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019
Database Server Requirements
Hardware requirements:
  • Minimum: 8 GB of RAM, recommended: 16 GB of RAM
  • 200 MB of available hard disk space. Depending on the number of transactions, additional hard disk space may be required to store large number of transactions.
  • Document Management, additional hard disk space depending on the amount of documents. 5GB of documents will require 5GB of additional storage. Consider this, Using an estimate of 2,500 pages per file drawer and four file drawers per file cabinet, one can estimate that scanning two four drawer file cabinets full of documents (ten thousand single sided pages) will require 1 GB.
The BirdDog database can be hosted by:
  • Microsoft SQL Server 2012, any edition
  • Microsoft SQL Server 2014, any edition
  • Microsoft SQL Server 2016, any edition
  • Microsoft SQL Server 2017, any edition
  • Microsoft SQL Server 2019, any edition

Full-Text Search needs to be installed on your SQL Server for our software to function correctly.

Back to Top

Work Station Requirements

  • 2gb of RAM
  • 2GHZ or better CPU
  • High speed internet
  • Windows 7 or later
  • If using Avatax, 64-bit is required

Back to Top

Web Browser Requirements

Web-browser Requirements for Ecommerce
Our publicly facing system can be accessed by any device with one of the following browsers:
  • Microsoft Internet Explorer version 9.0 or later
  • Mozilla Firefox version 10 or later
  • Apple Safari version 6 or later
  • Google Chrome version 17 or later
Web-browser Requirements for Enterprise
Our ERP system can be accessed by any device with one of the following browsers:
  • Microsoft Internet Explorer version 11
  • Mozilla Firefox version 10 or later
  • Apple Safari version 5 or later
  • Google Chrome version 17 or later

Back to Top