Version 16

16.2

16.1

16.0

System Requirements Version 16


16.2

Bug Fixes - Version 16.2.7 - Released 19 March 2022

This build has the following bug fixes implemented: 
Fixed
11847255 - Indexes Not Being Dropped And Re-Created Correctly On New BirdDog Databases Connected To An ERP
When using an existing ERP like Sage 100 that has previously had a connector sub-system run against it, when provisioning a new, blank BirdDog database and attempting to run against the ERP for the first time, a schema revision error was being thrown.

Back to Top


16.1

Bug Fixes - Version 16.1.25 - Released 19 March 2022

This build has the following bug fixes implemented: 
Better
11843127 - Removed Redundant SMTP Settings in Enterprise for Windows
Previously, Enterprise for Windows had two separate settings for email: one located at Settings | Email | Errors and one at Settings | Email | SMTPServer. We removed the former.
Fixed
11846383 - Salesperson on Customer Record Not Syncing to SvcPro
When changing the SalesPerson on a customer record in BirdDog, the ServicePro Connector did not Sync the change up to ServicePro.
Fixed
11846692 - M1 Sales Order Line Long Description Is Not Being Populated With The Parts Long Description
Orders synced into a M1 environment using the connector sub-system were not including the long description of the parts on the order.
Better
11846962 - Map WooCommerce Order.Customer Note To Sales Order Comments
Comments on a WooCommerce order were not syncing down to the local database when using the connector sub-system. Also removed the WooCommerce order number mapping to commments since it is already in the PO field.
Fixed
11847140 - Not All M1 Order Freight Fields Are Being Set
The M1 ERP supports freight at several different levels - multi-currency, freight at a line level, freight at a header level - and we were not handling that properly prior to this build.
Better
11847238 - Sales Person Not Defaulting Correctly From Ship To
When placing an order in sales order import with a .csv in Enterprise for Windows with a ship to that has a different salesperson than the customer, it defaulted to the customer's salesperson, and not the ship to's salesperson.
Fixed
11847531 - Amazon Connector Not Handling FBA Orders Correctly
The Amazon connector was previously ignoring orders with a status of "Shipped" which meant all FBA orders got ignored. We also fixed an issue where I-type orders were not auto-selecting bin and serial/lot transactions correctly.
Fixed
11848305 - FedEx Freight Rating Fails When Location Country Set to 3 Character ISO Country Code
FedEx expects a 2-digit country code - US, for example - but some ERPs allow for 3-digit codes - USA - and we were not handling that properly.

Back to Top

New Features

This branch has the following features implemented: 
Better
7642419 - Restored Ability to Add Items Using Enterprise for Macola ES/10 Sites
This is something that was deactivated an eternity ago due to how Macola ES/10 worked; now, you can once more add items to your ES environment using your local website pointed to that database.
New
11836330 - Link Customers on Org ID/OrgLocID
Added Downloaded_After event to WooCommerce
New
11845595 - Create Shopify Customer Linkage Import
Add Import Shopify Connector Customer Linkages to Enterprise for Windows | Utilities | Import | Connectors | Shopify | Customer Linkages and to web imports.
Better
11845620 - WooCom - Need Terms To Be Pulled From Order Rather Than Customer
This adds payment terms mapping that works the same as the ship via mapping for WooCommerce. Instructions for using this can be found here.
Better
11845877 - Record The US Post Office Freight Quote Request And Response
We added the database columns BDCarts.FreightQuoteRequest and FreightQuoteReturned a long time ago. However, we only implemented values for UPS and FedEx. Added support for the US Post Office.

Back to Top


16.0

Bug Fixes - Version 16.0.24 - Released 19 March 2022

This build has the following bug fixes implemented: 
Fixed
11837807 - Conversion From String To Type Error When Editing Item Qty in Customer Service
When using Order Entry and editing the quantity of a line item on a order, the system was throwing an ugly error when clicking Update Cart.
Fixed
11846073 - Schema Issue When Updating to 16
When updating a site to 16.0, was getting a create unique index schema error.
Fixed
11846165 - Typo in Shopify Download Warnings
Multiple typos in the 'not downloading' warning that needed to be fixed. Fixed them both.
Fixed
11846596 - Typo in CustomExamples Read Me
Customizations was misspelled in the readme.md

Back to Top

Bug Fixes - Version 16.0.16 - Released 10 December 2021

This build has the following bug fixes implemented: 
Fixed
11844381 - Editing An Existing Page With A Blank Code Should Default To Parent Code and Description
In version 12, we added the feature to automatically generate a webcategory code. However, this means that pages generated prior that and without the Code manually changed could still be showing the GUID. With this build, if you edit and save a webpage, the code will automatically be created.

Back to Top

New Features

This branch has the following features implemented: 
Better
11842955 - Schema Handling Update For Database Fields
Updated how we handle schema when dealing with an external ERP. Over the last two years, we've been expanding field lengths as we run into issues. The problem with doing it this way is that this means that sometimes we have fields that are longer than the ERP supports. For example, Customer numbers are length 10 in M1, 23 in Sage 100, and 24 in QuickBooks. Since 24 was the longest we'd seen, BD Engine used 24. This means that you can create customer # TESTIMTOOLONG in our system and then it will blow up writing to M1. As of this build, we'll create the database with BD Engine defaults but once you create an ERP connector, the system will automatically alter the database to match.

Back to Top

Upgrade Notes for Non-Macola Systems

Because some of the field lengths are getting smaller and it was possible to create values that were too long in previous versions, you may run into data that is invalid and causes the sql schema update to fail. When this happens, the system will report the invalid data which will need to be manually fixed in the database either by deleting it or updating it to a valid value.

This update is not compatible with prior versions. Once you run this version against a database, it is important to never run an older version of our software against that version.

Back to Top

Reason for Point Release

We've updated how we're handling schema when dealing with an external ERP. Over the last two years, we've been expanding field lengths as we run into issues. The problem with doing it this way is that this means that sometimes we have fields that are longer than the ERP supports. For example, Customer numbers are length 10 in M1, 23 in Sage 100, and 24 in QuickBooks. Since 24 was the longest we'd seen, BD Engine used 24. This means that you can create customer # TESTIMTOOLONG in our system and then it will blow up writing to M1. As of this build, we'll create the database with BD Engine defaults but once you create an ERP connector, the system will automatically alter the database to match.

Back to Top


System Requirements Version 16

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