Version 15

×

15.2

15.1

15.0

System Requirements Version 15


15.2

Bug Fixes - Version 15.2.9 - Released 19 March 2022

This build has the following bug fixes implemented: 
Better
11845346 - NullReference Error Syncing Tax Schedule Change on Customer from SvcPro
Improved the logging for errors when attempting to upload into Service Pro.

Back to Top

Bug Fixes - Version 15.2.6 - Released 10 December 2021

This build has the following bug fixes implemented: 
Fixed
11844963 - WooCommerce Connector Downloads Orders with Failed Status
The WooCommerce connector was still downloading orders that had "failed' statuses.

Back to Top

New Features

This branch has the following features implemented: 
Better
11844934 - Address 1 Too Long
Expanded table field length for the primary address on an order when using the BirdDog engine for your database.

Back to Top


15.1

Bug Fixes - Version 15.1.15 - Released 10 December 2021

This build has the following bug fixes implemented: 
Fixed
11837953 - Item Price Changes To 0 If Left in Cart and Processed After Timeout
A cart left unattended that timed out was causing serious issues with the Ecommerce checkout process.
Fixed
11844505 - Macola ES Entry Line Load Routine Is Not Using An On-Index Query
G/L Entry Lines (amutas) were being loaded by Journal and Entry Number. However, there is not an index for these two fields. Added the field EntryYear to the load query to get on index.
Fixed
11844935 - Attempting To Save An Existing Object, But The Record Cannot Be Found
Added better error handling for bad data for WooCommerce orders.

Back to Top

New Features

This branch has the following features implemented: 
Better
11840039 - Need to Write ShipVia From Woo Order Rather Than Macola Customer Default ShipVia
Added mapping for ship via codes for orders downloaded from WooCommerce. Consult these instructions to properly map them.
Better
11844069 - Add Ability To Set The Lowest Order Status That Should Be Selected For Billing During Interface Shipping
Previously, when interface shipping, if there was a tracking number, the order was processed regardless of status. In some environments, customers want to confirm ship the order before selecting it and they may enter the tracking number before they do that, thus, we updated the process end of day job to have a "Lowest Status to Select" parameter and only select orders that are that status or higher.

Back to Top


15.0

Bug Fixes - Version 15.0.29 - Released 25 May 2022

This build has the following bug fixes implemented: 
Fixed
11848249 - Sage Connector Needs To Re-Download All Sales Orders To Update Email Address
Update Order.OrderBy_Email to Pull From Order Table caused a data issue that required Sage 100 sales orders to be downloaded again.

Back to Top

Bug Fixes - Version 15.0.28 - Released 19 March 2022

This build has the following bug fixes implemented: 
Better
11843352 - Webnext Not Displaying Item Maintenance Page
When searching for an item in the Webnext interface the search returns a link to the requested item, but clicking on that link throws a "Not Found" error. Searching for and clicking on the same item in the web classic interface works as expected.
Fixed
11844063 - Customer Phone and Email Not Syncing Between BD and SvcPro
Adds downloading of Customer email from ServicePro; adds uploading of customer phone, ext, and email to Service Pro.

Back to Top

Bug Fixes - Version 15.0.27 - Released 10 December 2021

This build has the following bug fixes implemented: 
Fixed
11838323 - Customer Service Isn't Handling Tax Code 0 Correctly
The ES/Synergy integration allows customers to be created with a tax code of 0 (Unknown). This should be illegal according to the ES Customer interface but, nonetheless, is seen in the wild all the time, so we updated to handle Tax Code 0 as blank or default.
Better
11839882 - Shipper Showing as Unknown for Uploaded WooCommerce Order
The WooCommerce connector uploads a tracking number and ship date, but the shipper was showing as Unknown and the WooCommerce order was still listed as Processing.
Fixed
11842782 - Item Description Not Syncing Between BirdDog and ServicePro
Item Description was syncing up to ServicePro correctly during initial item sync, but any changes made to that Description afterward did not go up to ServicePro.
Fixed
11843311 - Invoices Won't Upload When Posted Before the Sales Order is Uploaded
When an order is created in BirdDog and invoiced/posted before JobMaster fires Run Connectors, an Invoice was not getting created in QuickBooks and it throws errors in logging about missing linkages.
Better
11843620 - Sales Person Commission Percent Being Lost
In Macola ES/10, when Selecting an order using BirdDog, the slspsn_pct_comm field was being set to the sales person's commission percentage when this field actually means "what percentage of the order does this sales person get commission on" and should be 100 if there is only one sales person.
Fixed
11843948 - WooCommerce Connector Doesn't Update Itemtype on Item Linkage if the Linkage Already Exists
In version 14, we added the abiity to download item linkages for WooCommerce. That process worked great for new customers but did not convert the data for existing customers correctly.
Fixed
11844062 - Shipping Interface Doesn't Honor Freight Quote on Web Orders When Processing Manifest Transactions
When running shipping interface and it pulls in tracking numbers from BDShipInterface, it does the following: Totals the freight charges on all tracking numbers for an order and sets the order freight to that amount unless it is an ecommerce order with a non zero freight amount. When running shipping interface and processing existing manifest transactions from ARShtFil_sql, it should have followed the same logic but instead was adding the freight of all the transactions to the order (not overwriting) and it was doing this for Ecommerce orders as well.
Fixed
11844065 - YourReference on Macola 10 Bank Transactions Table Not Populating Correctly When Posting
This should have contained the sales order PO number, but it was blank.
Better
11844635 - Taxable Flag Not Set on Customer Synced From Sage
When syncing a customer from Sage 100 to BirdDog, the Taxable Flag is not getting set on the Customer in BirdDog. This is due to Sage not really having a concept of "taxable" on Customers and just expecting a Tax Schedule set on every customer. This was causing an issue in the ServicePro interface where if you go into the Customer record in SP and make a change, the UI won't allow you to close the page (and save the change) because it expects an "Exempt Number" to be set on a Customer that is not set to Taxable. Rather than just turning off the UI validation of that Exempt Number field on most customer's systems in ServicePro to avoid any complaints, we are now marking all customers as taxable.
Fixed
11845041 - QuickBooks Desktop Throws Error When Sales order Line Doesn't Have An ItemRef
Observed in a QuickBooks environment with sales order line data that was missing the reference to an item. We thought that was illegal and didn't test for it. We now handle that data.

Back to Top

New Features

This branch has the following features implemented: 
Better
11838221.1 - Confirm Ship Enhancements
We made a number of improvements to the Confirm Ship functionality:
  • Add sales order number entry to Warehouse Management | Shipping | Confirm Ship that allows you to enter or scan a single sales order number.
  • Updated the confirm ship order page header to match order view.
  • Add ability to edit comments on confirm ship (Header comments, ship instruc 1/2, comment 1/2, a/r comments 1-3).
  • Updated the confirm ship order page to record lock the order.
Better
11838221.2 - Customer Service Order/Invoice View Enhancements
We made a number of improvements to the Customer Service order and invoice view:
  • Add Ship Date and void column to the ecom/customer service order/invoice on the tracking number list.
  • Updated Order Edit to unconfirm ship a confirm shipped order when clicking the edit button and the status of the order is Shipped.
Better
11838221.3 - Shipping Interface Enhancements
Updated the select for billing process to not select order lines that weren't confirm shipped.
Better
11838221.4 - Record Shipment Enhancements
Updated record shipment to write to the manifest trx instead of ship trx. Prior to this enhancement, Warehouse Management | Warehouse | Record Shipment wrote the tracking number to the BirdDog Shipping Interface table. While this worked great for the end of day process, it was lousy from a user experience since it didn't show up on the Order View screen in Customer Service or Ecommerce until after the end of day process was ran. With this update, we write it instead to the A/R Shipping Table with a status of unprocessed. This makes it to where it immediately shows on the Order View screen but will also still be used as a trigger for the end of day process.
Better
11840821 - Refactor Process End of Day Job
This is a massive refactor of the Process End of Day Service (not menu item in Enterprise for Windows) that makes major output changes to the individual components of the process end of day job as well as the job itself. Also added verbosity support for the job and all of its components. For example, if you have the Process End of Day job set to a verbosity setting of Activity and you process some orders from shipping interface to post but they don't have any credit card authorizations, you will get the individual reports such as shipping interface, invoicing, and posting, along with the process end of day summary but you won't get a report for the capture process.
New
11840858 - Update Order.OrderBy_Email to Pull From Order Table
Prior to this build, the ordered by email that shows on the customer service order form pulls from Ordered_ByEmail field on the Carts table. We updated the system to write that to the order when converting a cart to an order in Ecommerce/Customer Service.
Better
11843393 - Production Order Customer Number Field Not Long Enough
Expanded BirdDog engine field lengths in PPOrdFil_sql, IMOrdBld_sql, and IMOrdHst_sql.
Better
11843401 - Post Sales Orders for Macola ES is Not Populating Some Fields Correctly
There were a handful of fields that were not populating on the BankTransactions table during posting with BirdDog software.
Better
11843403 - Add Feature Switch to Disable Auto Freight Rating on Sales Orders
When licensed for the Freight Module, our system recalculates freight anytime a sales order is touched. There are scenarios where this is less than ideal, such as when a customer is licensed for Freight and using our Confirm Ship system, but they are not using our Picking System. This scenario breaks some assumptions that cause freight to be doubled during the end of day process. We need to move from freight being implicitly calculated on a sales order to it being calculated expliclitly. However, this is a massive change that will generate a lot of bugs until we chase down all the places that have to be fixed, so instead of making a hard change, we've decided to add a feature switch. For now, all customers will continue to operate the old way unless the feature switch is enabled with the script here.
New
11843498 - Add Ability to Resend CommerceHub Invoices
The CommerceHub environment will accept an invoice and then later send an email that it didn't like something about it. Once the configuration has been fixed you need to update the BD Connector Linkages table to force the CommerceHub Connector to resend them. CommerceHub will email a response. We added the ability to paste in the body of the email and force all of the corresponding linkages to the proper state so they will resend the invoice.
Better
11843552 - Update WooCommerce Connector to Use Default Tax Code If Customer is Set to a Tax Schedule
WooCommerce does not support tax schedules, but some of the ERPs that we connect to only use them and our original pass of the connector presumed that both were an option for Woo. Now, if Customer is set to a single tax code, we use that tax code on the sales order and set the tax amount and percentage; if Customer is set to multiple tax codes or a tax schedule then we use the tax code from the connector account on the sales order and set the tax amount and percentage; additionally, the WooCommerce connector no longer supports a default tax schedule, only a tax code. If you were previously set to a tax schedule it will throw an error on every run until you set a tax code. This does not apply to customers running Sage 100 as it only supports tax schedules.
Better
11843620 - Sales Person Commission Percent Being Lost
In Macola ES/10, when Selecting an order using BirdDog, the slspsn_pct_comm field was being set to the sales person's commission percentage when this field actually means "what percentage of the order does this sales person get commission on" and should be 100 if there is only one sales person.
New
11843731 - Add Support For Starting Order to the WooCommerce Connector
Add support for starting order on the connector to avoid the system trying to download the entire history from WooCommerce. Any order before the starting order is ignored.

Back to Top

Upgrade Notes

When licensed for the Freight Module, our system recalculates freight anytime a sales order is touched. There are scenarios where this is less than ideal, such as when a customer is licensed for Freight and using our Confirm Ship system, but they are not using our Picking System. This scenario breaks some assumptions that cause freight to be doubled during the end of day process. We need to move from freight being implicitly calculated on a sales order to it being calculated expliclitly. However, this is a massive change that will generate a lot of bugs until we chase down all the places that have to be fixed, so instead of making a hard change, we've decided to add a feature switch. For now, all customers will continue to operate the old way unless the feature switch is enabled with the script here:

INSERT INTO [dbo].[BDSettings]
           ([ID]
           ,[Name]
           ,[Value]
           ,[Node]
           ,[Group]
           ,[Instance]
           ,[Description]
           ,[IsEditable]
           ,[DataType]
           ,[SettingType]
           ,[LastUpdate]
           ,[RecordRevLevel]
           ,[FriendlyName])
     VALUES
           ('0F6E89F3-3754-4EFF-A358-2DA3F98EBFC9'
           ,'Disable Auto Calculate Freight'
           ,'1'
           ,''
           ,''
           ,''
           ,''
           ,1
           ,3
           ,2
           ,GETDATE()
           ,0
           ,'')

Back to Top

Reason for Point Release

This build expanded BirdDog engine field lengths in PPOrdFil_sql, IMOrdBld_sql, and IMOrdHst_sql.

Back to Top


System Requirements Version 15

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