Version 19

×

19.1

19.0

System Requirements Version 19


19.1

Bug Fixes - 19.1.27 - 30 September 2022

This build has the following bug fixes implemented: 
Fixed
11847021 - Able To Place Order Without Choosing A New Shipto Address
Orders created by an Ecommerce user where an alternate saved shipping address was selected were not generating with this correct address, which made receiving items difficult.
Fixed
11851956 - Amazon Connector Not Pulling Down Shipping Charges on Orders
When using the Amazon connector, freight charges were not coming down correctly to the local ERP.
Better
11853509 - Country Location Does Not Handle Quotation Marks In Name
Unusual scenario where the original ERP environment being utilized had apostrophes in the order address. BirdDog wasn't handling that correctly when pointed at it.
Fixed
11853767 - M1 Connector Won't Delete Jobs That Have Been Released
Fixed an issue where if the job was released and then deleted in M1 it did not get deleted in BirdDog.
Fixed
11854134 - Remove View Invoices In Enterprise for Windows
This functionality has been removed entirely from Enterprise for Windows. Note: Be advised that if you run older code against the database after this has been removed, the older code will add it back.
Fixed
11854294 - M1 Connector Not Handling International Data Well
Customers with non-US countries in M1 were getting changed to the United States in the course of the connector run. Essentially, country codes in M1 have considerably larger field lengths than the core BirdDog engine is accustomed to, so the connector was presuming the information being downloaded was wrong and in the process ended up defaulting back to US. Now it throws a warning and skips that customer.
Fixed
11854986 - Posting Not Setting All Fields On The Header And Line correctly
When posting an invoiced order in BirdDog and comparing it to a posted order in Macola, we were noting some inconsistencies with OE Header History and OE Line History tables.
Fixed
11855142 - Sage 100 Timestamp Not Being Set On Legacy Sales Orders Causing Sync Loops
In an earlier version, we added an optimization to track changes on the Sage 100 side of the connector to keep from downloading when we didn't need to. There was a logic error in this code that caused some issues with changes that appeared in more recent versions. These issues created a scenario where a customer upgrading from an earlier version using a current version of our software could experience a download loop if they were using more than one connector and changed an old sales order.

Back to Top

New Features

This branch has the following features implemented: 
Better
11846560 - Add Support To Choose Which Order Statuses We Download From Woo
This adds a comma-separated list of order statuses to the WooCommerce connector screen. Only orders with a status that match something in this list will download. Orders with a status that does not match will be reported to the log. This also fixes order downloads not using a change date and downloading, but not processing every order from woocommerce on every run. And finally, this fixes item downoads not using the change date correctly and downloading, but not processing every item on every run.
Better
11847472 - Sage Connector Downloading Tax Schedules Every Run
Sage 100 doesn't have "last update date/time" properties on Tax Schedules and Codes so we have no idea when they changed. Prior to this enhancement, we would download them on every run and compare them to what we have. For most customers, this happens fast enough that no one notices. This enhancement adds BDConnectorAccounts.TaxInfoDownloadWaitMinutes. There is no interface for this value because we normally do not anyone messing with it. If this value is set, then the connector will wait that many minutes before downloading Tax Schedules/Codes again. Instructions for setting this up can be found here.
New
11848657 - Add New Setting To The WooCommerce Connector That Controls Handling of WooCommerce Guest Orders
Added a new setting to the WooCommerce connector. In addition to Next Customer Number and Guest Customer Number on the dropdown list for Guest Customer No, we've added "Guest Customer Number With Ship To." Using this will still require the guest customer number to be added in the connector setup, but the system will now add a ship to to the customer for each new guest customer on WooCommerce. When adding a new ship to the system searches the guest customer for a ship to that has a matching email address. If one is found then it uses it. If one is not found it adds the next ship to number (starting at 1000) and sets the address to the ship to address of the order.
Better
11849893 - Add Interface to Shopify Connector to Select What Item Data to Upload
With this build, you can amend the level of item data you wish to push up to Shopify using the connector sub-system.
Better
11850375 - Set Items As Obsolete When Effective End Date Is Set In M1
Added mapping for M1 Part Revisions Effective End Date to Activity Code and Date. If the Effective End Date is set in M1, then we mark the item as obsolete and set the activity date to the Effective End Date.
Better
11852374 - When Requested Ship Date On Sales Order Header Is Changed, Lines With A Matching Date Should Change
This changes the default behavior of the order/cart object. When changing the default shipping date on the header, any lines with a matching request date will be updated as well. Prior to this, the shipping date on the header was only used as the default request date on new lines.
Better
11852746 - Add Standard Shipping Days To The ATP Calculation
Added "Standard Shipping Days" to the Manage Picking page on Warehouse Management which defaults to zero. Whatever value is plugged into that is then added to the Available to Promise (ATP) calculation.
Better
11853061 - Add Picking Sequence Column to Item/Location Import Template
Improved the existing import.
New
11853224 - Sage 2022 Compatibility
As of this build, our connector sub-system is fully compatible with Sage 100 2022.
New
11853690 - Enhancement To Add JobMaster Support For Purchase Order Integrator
BirdDog has long supported an interactive import of Purchase Orders using Enterprise for Windows. This enhances that process to support automatically reading files from a directory with Job Master.
Better
11853596 - Set Items As Obsolete When Inactive Is Set In M1
Added mapping for M1 Part Revisions Inactive flag to Activity Code and Date. If the Part Revision is marked inactive, then we mark the item as obsolete and set the activity date to the Effective End Date; if Effective End Date is not set, then we use today's date.

Back to Top


19.0

Bug Fixes - 19.0.10 - Released 19 September 2022

This build has the following bug fixes implemented: 
Better
11847501 - Tax Exempt Number Field Not Passing between BirdDog and Sage
A new customer created in Sage 100 with a tax exempt number was not syncing up to BirdDog with that number the appropriate table. If an customer was generated in BirdDog or a different system (like Service Pro) with a tax exempt number and synced down, it would bring that number down to Sage, so this was only an issue going one way. Additional information regarding setup for this can be found here.
Fixed
11851850 - ConfirmTo Field In Sage100 Gets Overwritten When Syncing Order To SvcPro and Back
This bug was discovered following a specific scenario: an order was generated in Service Pro, synced down to Sage 100 and then adjusted by adding new data to the 'Confirm to' field there was not syncing back up to ServicePro with that information. Further, this required both connectors to be enabled as if they were run one at a time - so one is disabled until after the connector was run, and then it was disabled and the other was enabled for a second connector run - this worked fine, so it was clear that the data was stepping on itself.
Better
11852476 - Cart.Ordered By Name is Defaulting to Customer.Name on Shopify Orders
On an order downloaded from Shopify, the Cart.Ordered_byname was defaulting to Customer.Name and should have been defaulting to Customer.Contact. Our fix low involves a level change to how the Cart functions which changes the way OrderedBy info (name,email,phone) gets defaults. This removes scenarios where ordered by name default to the customer name. It also removes any defaulting of OrderedBy info when the User has the customer service role.

Back to Top

New Features

This branch has the following features implemented: 
New
11843367 - Add Order.Applying and Applied events
The behavior of the custom event Order.Placed has changed. You are now required to call ApplyEdit on the order if you make any changes. This is a breaking change.
Better
11843764 - Sync More Fields Two-Ways With ServicePro Customers and Orders
Improved syncing for Customers, Ship-Tos, and Sales Orders when using the connector sub-system for ServicePro environments.
Better
11845345 - Upgrade Crystal Reports
Upgrades our systems to use Crystal Reports 13.31.
Better
11846951 - Move SendEMailConfirmation From Web Down To Cart
This is a development change that leaves existing behavior unchanged for email confirmations on new orders from ecommerce and customer service. This also adds a new job "Convert a cart to an order" that allows you to process a single cart to order.
New
11850404 - Support Writing Credit Card Cash Receipts to Sage 100
We added the ability to capture credit cards for Sage 100 Ecommerce customers in 11846176 Auth Card In The Ecom Site And Capture When Invoiced in External ERP released in 18.1.14 when invoiced in Sage 100. This project completes the accounting loop for those transactions.
Better
11851694 - Sage Item Extended Description Not Pushing Up To BD Correctly
Extended the item description field length throughout the system to 4096 for Sage 100 to enable support for extended descriptions. Updated the Sage connector to use the extended description, if it exists, for items, sales order lines, and invoice lines.
Better
11852767 - Invalid Project Code Error Downloading Orders with a Job Number From Sage
This branch adds the "auto-adding" of missing projects when downloading from Sage 100. Job Number was Sage functionality that we'd missed in previous versions of the software because, until recently, none of our clients actually used it in their Sage environments.

Back to Top

Reason for Point Release

This point increase (v18 to v19) was principally caused by three projects: 11845345, which upgrades BirdDog code to handle Crystal Reports 13.31; 11843367, which modifies the behavior of the custom event Order.Placed; and 11851694, which greatly extended the item description field length.

Back to Top


System Requirements Version 19

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