Version 11

×

11.1

11.0

System Requirements Version 11


11.1

Bug Fixes - Version 11.1.45 - Released 15 April 2021

This build has the following bug fixes implemented: 
Better
11834744 - Enterprise for Windows Selecting Entire Order Instead of Just Lines That Are Shipped
When using a customization that automatically Selected an order when the ShippingEasy Connector was run, we discovered that our process was Selecting the entire order instead of just lines that were shipped. This was important if a customer, for example, split up an order in ShippingEasy and shipped out only some of the lines on the order.
Fixed
11834946 - Report Could Not Be Found Error on Print Order Acknowledgement
When trying to print an Order Acknowledgement, it failed with a "Report could not be found" error even though report paths were set up correctly in Enterprise for Windows, report files exist in the specified folder and the FormType is set to the correct filename in Enterprise for Windows | Maintain | Setup | Distribution Forms.
Better
11835387 - Shopify Connector Pulled Weird Tax Percent
Updated the process of setting tax on an order being downloaded from Shopify using the Shopify Connector to not error out if the percentage can't be represented; it now reports a warning and downloads the order.
Better
11835520 - Order Line Changes Cause the Amazon Connector to Throw Errors on Every Run
Unreconcilable errors caused by order changes were showing up on every Amazon Connector run. They are now reported as an error one time.
Fixed
11835596 - Cart.CopyHeader Missing Properties
A low-level function that duplicates shopping carts was missing a handful of properties such as Bill_To_Addr_3, Ship_To_Addr_3, Sales_Person_No, Ship_Via_Code, Loc, and Taxable.

Back to Top

Bug Fixes - Version 11.1.35 - Released 18 February 2021

This build has the following bug fixes implemented: 
Better
11714427 - Pricing Changes Not Uploading to Magento
When using the BirdDog Connector Sub-System for Magento, changes made to prices in the ERP were not syncing up correctly.
Fixed
11826763 - Estimated Duration on IncidentForm.aspx Not Populating Correctly
The Estimated Duration field on the Incident Form page was not properly autocalculating into a proper date format based on Due Date minus Start Date and instead, displayed as (for example): 2020y 41w 2d.
Better
11829826 - Error Uploading Sales Order Due to Duplicate Key Exception
Adjusted the code to handle bad data better with M1 using the BirdDog Connector Sub-System by changing an Error (that stopped all progress of the connector run) to a warning.
Fixed
11832020 - Items in Saved Cart Use Saved Cart Price on Checkout Instead of Current Price
When creating a new cart from a saved cart, items in the new cart were using the saved cart price, rather than using the current item price.
Fixed
11833436 - Unable to Save Changes Made to Addresses on Address Book Page
In Ecommerce, when editing saved Ship-Tos in the Address Book, clicking Save didn't make the edit screen disappear and changes weren't saved.
Fixed
11833910 - M1 Connector Not Updating the Default Location in Inventory Setup
Some default data in Inventory Setup was not being set correctly to match data in M1 using the BirdDog Connector Sub-System.
Better
11834220 - Macola ES/10 Customer with Invalid cnt_id Has Issues Logging Into Ecommerce
The value in cicmpy.cnt_id should normally match a value in cicntp.cnt_id. If it doesn't, you have invalid data. When a user connected to a customer with invalid data like this attempts to login, they get weird errors and had to log in twice.
Fixed
11834402 - Avalara Cert Capture Requires A Customer Have An Email Address To Upload
Previous versions of the software required an email address for any customer to be uploaded since Avalara CertCapture can send certificate requests via email. However, this caused integration issues when customers were uploading existing sales tax certificates to CertCap for customers without an email address on file. Email addresses are no longer required to upload a customer to CertCapture.
Better
11834767 - CartCapture Connector Not Pulling Down Customer Certs
Added additional logging to explain why a cert was not being downloaded using the BirdDog Connector Sub-System against Avalara CertCapture.
Better
11834768 - Shopify Connector Throws Ugly Error When Missing Customer
When a customer was deleted on the ERP side (for whatever reason), the BirdDog Connector Sub-System was throwing an ugly error when trying to download a new order from Shopify using that customer.
Better
11834838 - POS Section on Enterprise for Windows Crashing
Removed some old code from Enterprise for Windows because it was no longer valid.
Fixed
11834846 - CASH POS Table Posdrawers Missing
Some required database tables for BirdDog Cash were not being generated using other software - Enterprise for Windows, Job Master, the web - so we adjusted our Cash code to auto-generate these tables when initially run against the database.

Back to Top

Bug Fixes - Version 11.1.24 - Released 11 January 2021

This build has the following bug fixes implemented: 
Better
11736444 - Formatting Inconsistency When Importing Wire Payment with Auto Cash Receipts
When using the Auto Cash Receipts import tool with Macola Progression, the [reference] field that is set in the [ARCSHAPL_SQL] table when importing a Wire payment (code=W) did not match the standard format that Progression uses.
Fixed
11831076 - Typo in Error Regarding "External Access" in Sage
Fixed a typo in an error message. Company was misspelled.
Fixed
11831796 - Woo Commerce Orders With Line Quantities Get Changed to 0
Orders generated in Woo Commerce that were pulled down into a Sage 100 environment while using the BirdDog Connector Sub-System were writing into Sage with 0 quantities.
Fixed
11833421 - Saved Ship-To on Cart Not Getting Re-Selected When Navigating Away and Back to Checkout
At Checkout, if you selected a Ship-To other than the default and then navigated away from the Checkout page and back to Checkout again, the Ship-To displayed under Shipping Information reverted back to displaying the Default Ship-To (or No Address Selected, if there is no SelectedShipTo assigned to the cart), but the system still used the Ship-To that was selected before navigating away from Checkout (i.e. freight rating is still for the selected Ship-To, even though the default Ship-To is now being displayed under Shipping Information). Now, the system keeps the Ship-To that you've selected.

Back to Top

New Features

This branch has the following features implemented: 
New
11829700 - Sage 100 Contacts to BirdDog Contacts
Contacts created or edited in Sage 100 now write up to the BirdDog environment when using BirdDog Connector Sub-System.
New
11829702 - Upload BirdDog Contacts to WooCommerce Users
With this build, we updated the BirdDog Connector Sub-System to upload all BirdDog Contacts that have a relationship with an Organization that have a Customer Number. When downloading an order from WooCommerce, we assign the order to the customer number that the contact is related to. If the contact is related to more than one customer, we then use the Customer that the User is linked to, and if the contact has more than one User/Customer, than we report an error and don't download the order until it is corrected.
New
11829708 - Macola ES Contacts to BirdDog Contacts
With this build, we mapped Macola ES customer contacts to BirdDog contacts. A connector entry must be created for BirdDog Connector Sub-System for this functionality to work.
New
11830766 - BirdDog Contacts to Sage 100 Contacts
Contacts created or edited in BirdDog now write down to the Sage 100 environment when using BirdDog Connector Sub-System.
New
11831451 - BirdDog Contacts to Macola ES Contacts
With this build, we mapped BirdDog contacts back to Macola ES contacts. A connector entry must be created for BirdDog Connector Sub-System for this functionality to work.
Better
11833491 - Make Number of Addresses Required to Trigger Filter Versus DDL Configurable and Default to 20
The My Account>Address Book has two different layouts depending on the number of addresses you have: list all or search. Before this update, the system switched from the list to the search when you had 5 or more addresses. This update increases that threshold to over 20. We also added the ability to customize this setting; see this page to see how to use this.
Better
11833824 - Add Support for utm_cid Being a User ID to the Process Page Hits Job
Previously, the utm_cid as a query string parameter needed to be a value from the BirdDog BRAIN campaign system. We updated the process page hits job to support this value also being a BirdDog User ID to support integrating with email systems such as Constant Contact or Mail Chimp.
New
11834118 - Add Out Sick Status
For use with the timesheet functionality in BRAIN, we added an Out Sick status that works pretty much the same way as Out for the Evening or Out on Holiday.

Back to Top


11.0

Bug Fixes - Version 11.0.45 - Released 15 April 2021

This build has the following bug fixes implemented: 
Better
11833858 - ServicePro Getting Errors on a LOT of Orders During Initial Download
When running an initial download against an existing Service Pro company for a new BirdDog database using the Service Pro Connector, a considerable amount of orders threw a "You cannot change the sign of quanitity ordered on an existing line" error.
Fixed
11835763 - Unable to Download Sage GL Account 0000
When attempting to download a G/L account from Sage 100 using the Sage 100 Connector with a Main Account Code of 0000, the connector threw an error and didn't download the G/L account.
Better
11835785 - Blank Sage ARDIVISIONNO on ShipTo Throws Unhelpful Error
Updated the Sage 100 Connector to handle invalid Ship To data better and report as a warning.

Back to Top

Bug Fixes - Version 11.0.39 - Released 11 January 2021

This build has the following bug fixes implemented: 
Fixed
11834144 - Drop Index Error on IMItmIdx_Sql.pk_imitmidx_sql
This fixes potential revision errors when updating older BirdDog databases.

Back to Top

Bug Fixes - Version 11.0.33 - Released 22 December 2020

This build has the following bug fixes implemented: 
Better
11604112 - Changed Fields Not Syncing Correctly
When a field was synced down to Sage 100 from Service Pro via the BirdDog Connector Sub-System and it was changed in Sage, instead of syncing this new information back up to the Service Pro order, the changed data was being overwritten by the original data. While technically a bug fix, the amount of coding adjustment necessary to resolve this prompted a new branch.
Fixed
11829871 - Inconsistent Orderline Sync to Sage on Miscellaneous Items
When adding Orderlines that contain Miscellaneous items on an order in Service Pro, occasionally orderline data is not getting synced completely and sometimes an orderline doesn't go to Sage at all.
Better
11830520 - Update Framework SDK Documentation to Cover How To Set Audit User
Updated the application controller (AppCon.vb) example code to show how to load a user from the current windows user. Updated the Getting Started docs to better explain what the Application Controller is responsible for.
Better
11831355 - Required Ship Date Should Default From Request Date, Not Promise Date
When you ran "Fill Back Orders", the Promise & Required Ship Dates were not updated which could prevent the item from getting picked. While reviewing this, we determined that the Required Ship Date was defaulting from Promise Date instead of Request Date.
Fixed
11831746 - Inventory frz qty Not Impacted on PO Recv transactions
When receiving inventory against an item/location that was currently frozen if the transaction date was before the freeze date, the frozen quantity and cost were not being updated.
Better
11831799 - Form Number For Send Request Button Should be Settable
In Enterprise for Windows, the Send Request button on Maintain | Customers | Tax Certifications was hard-coded to submit "Form #48", which used to be Avalara's default request form. We changed that to be a value that can be set in the BirdDog Connector Sub-System screen for Avalara CertCapture.
Better
11832342 - CertCapture Customer Upload Should Allow Non-Taxable Customers
This was a design flaw. By only uploading tax-exempt customers to CertCapture, we required our customers to set the customers they want to track to tax-exempt. This caused Macola to default all orders to tax-exempt. When communicating with AvaTax, we send the tax-exempt flag on the order which essentially sets every transaction as tax-exempt.
Better
11832944 - Bug in Index Creation Causing Intermittent Database Revision Errors
A bug in a specific process was causing the database revision process to create indexes with incorrect names which was causing certain schema changes to fail.
Better
11833479 - Improve CertCap Test Response
When using the BirdDog Connector Sub-System against Avalara CertCapture, you are able to test your CertCap credentials in the connector screen but it did not give you any idea what the issue was if something was wrong. We updated the test button to include the error message when it fails.
Fixed
11834138 - BDUserCustomers Table Missing Unique Index on UserID and Cus_No
These missing indices caused two issues: the system could create duplicate records and performance problems on larger sites.

Back to Top

New Features

This branch has the following features implemented: 
Better
11831207 - Convert the Sage 100 Connector From Trigger Audit to Row Version Sync
When the Sage 100 Connector was created in 2018, it was built upon the synchronization engine used by our Ecommerce platform for almost two decades. We refer to this system as Trigger Audit internally. This system was built with two purposes - audit row-level changes for every watched table and trigger synchronization based upon those changes. The change tracking was very helpful for auditing issues in an Ecommerce environment where it is difficult to get steps of what happened from an end user. The downside was that it generated a lot of data and the conversion of the audit logs to change events didn't always perform very well. Another issue was that the Ecommerce environment was almost exclusively a one-way sync - item and customer data would go up and sales orders would come down. The addition of two-way sync for customers, ship tos, and sales orders in 2019 across multiple connectors exacerbated the downsides of the trigger audit system. Because of these issues, we went back to the drawing board and created a system that was tightly focused on handling change events in the most efficient manner possible. We refer to this system as Row Version internally. This system was first deployed to our M1 Connector in 2019 with great success. With the completion of this project, the Sage 100 Connector has now been fully converted to the Row Version system. The change from Trigger Audit to Row Version requires a data conversion. This conversion is completely automatic but does require a managed cutover from a prior version. This data conversion is what caused the point increase from 10.x to 11.x. For customers that are not using the Sage 100 Connector, 11.x can be treated as a point release to 10.x.
Better
11831208 - Convert the Service Pro Connector From Trigger Audit to Row Version Sync
Similar to 11831207 above, but for Service Pro instead of Sage 100. The change from Trigger Audit to Row Version requires a data conversion. This conversion is completely automatic but does require a managed cutover from a prior version. This data conversion is what caused the point increase from 10.x to 11.x. For customers that are not using the Service Pro Connector, 11.x can be treated as a point release to 10.x.
Better
11832032 - Add Command Line Call for Tax Certifications Screen
The Enterprise Windows client already allows for command line calls as noted here, but this build adds the Maintain |Customers | Tax Certifications functionality for use with Avalara CertCapture.

Back to Top


System Requirements Version 11

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

Installation

Before you start
Before starting the installation process, we recommend you install all critical up-dates for the operating system and software components.
Before installing BirdDog system server software, make sure that the following software is installed and enabled:
Installation
  • Software Installation requires Terminal Services access with administrator rights, username, password, and address. As well as Enterprise Manager and Database access with administrator rights
  • Local installs require Terminal Services listed above as well as FTP access to web server where staging site will be held with read and write access. FTP address User Name and Password.
Ecommerce
  • Staging sites are set up against the live database
  • SSL certificate is required for a secure website. If requested, BirdDog will provide assistance in obtaining a certificate. BirdDog is not responsible for provider selection, certificate selection or payment of SSL certificate
  • Pricing is taken directly from the data in the Database. BirdDog software can use both the price from the default location, usually as the suggested price, and use the pricing from the price code for the actual sales price
  • The default location price is the price in the default item location file
  • The price code price is processed per settings from Price Code Maintenance, and Setup for the order, or Priority, and selection method of the price codes
  • Tax schedules and detail codes must be set up for sales tax to calculate appropriate tax
  • Online credit card authorization requires BirdDog CardAuthorize module and a supported Credit Card gateway
  • Shipment Tracking numbers are dynamically ‘clickable’ from web site after they are written to the Shipping Manifest System
  • Freight rates are based on item weight and item packaging information set up in BirdDog Item Maintenance
Website Hosting Options
  • BirdDog Hosted Solution- BirdDog is installed on your local server. Data is synchronized to your website. Orders gathered on your web site are written directly into your local database
  • Local Installation - web server requires high-speed (10 mgb or greater) database connection to Macola serve
CASH Point of Sale
  • Credit card transactions require a supported gateway
  • If using Authorize.NET as your gateway, account type must be retail –not phone or ecommerce
  • Requires a network connection
Macola
  • Software Installation requires Terminal Services access with administrator rights, username, password, and address. As well as Enterprise Manager and Macola access with administrator rights
  • Local installs require Terminal Services listed above as well as FTP access to web server where staging site will be held with read and write access. FTP address User Name and Password.
  • Macola table and field names have not been customized
  • Pricing is taken directly from the data in Macola. BirdDog software can use both the price from the default location, usually as the suggested price, and use the pricing from the Macola price code for the actual sales price
  • The default location price is the price in the default item location file
  • The price code price is processed per settings from OE Price Code Maintenance, and O/E Setup for the order, or Priority, and selection method of the price codes
  • Tax schedules and detail codes must be set up in Macola for web site to calculate appropriate tax
  • Online credit card authorization requires BirdDog CardAuthorize module and a supported gateway
  • Shipment Tracking numbers are dynamically ‘clickable’ from web site after they are written to the Macola Manifest System
  • Freight rates are based on item weight from Macola and item information set up in BirdDog Item Maintenance
  • Picking System requires inventory to be correct inside Macola
Custom Development

To ensure a timely completion of the import project our developers require a current backup of your Macola database to be used for internal testing. The ability to test the customizations against your data greatly speeds up the roll out process

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