Version 21

×

21.0

System Requirements Version 21

21.0

Bug Fixes - 21.0.48 - Released 4 June 2024

This build has the following bug fixes implemented: 
Fixed
11875998 - Update UPS API Call To Support OATH 2.0
UPS is deprecating access key authentication in favor of an OAuth 2.0 security model for all APIs as of 5 August 2024, at which point access keys will no longer be supported for authentication to any UPS APIs. As a result, we implemented a critical fix to our existing UPS freight account functionality to ensure it continues to work. We no longer need any of the information previously required; instead, there is now a button on the UPS freight account page that will send the user to UPS to authorize BirdDog to access the data. Authorization then takes you to the BirdDog home page and upon logging in with the email address we have on record, your system is fully authenticated and you are redirected back to your site. Apart from this, UPS rating is unchanged in BirdDog.

Back to Top

Bug Fixes - 21.0.45 - Released 27 April 2024

This build has the following bug fixes implemented: 
Fixed
11863633 - QBD Connector Throwing Unhelpful Error Running QB Inventory-Assembly Module
This ended up being unexpected NULLs coming from QuickBooks Desktop Connector on Inventory Assemblies.
Fixed
11872721 - WooCommerce Connector Sends Item Master Data When Set to None
The Send Item Master Data functionality on the WooCommerce Connector only applied if you didn't manipulate the database directly or for the first download.
Fixed
11867643 - Create Categories30.aspx (File Upload)
This layout was accidentally removed at some point. This adds its functionality back.

Back to Top

Bug Fixes - 21.0.42 - Released 19 February 2024

This build has the following bug fixes implemented: 
Better
11869037 - Update Shipping Interface To Run Periodically Instead Of At The End Of Day
Shipping Interface was originally built for the UPS Worldship and FedEx Ship Manager to export all tracking number data at the end of day. This enhancement allows the tracking information to be exported throughout the day in order to increase shipment visibility.
Better
11870358 - Sage Connector Adding Tax Rates Together When There is a Taxable Freight Record Checked on the Tax Code
Updates the Sage connector sub-system to ignore tax rates from tax classes NT (Nontaxable) and TF (Tax Freight) when downloading tax codes from Sage 100. If the TF (Tax Freight) class has a non-zero tax rate, then we set the Tax Freight flag. In addition, we check to see if the TF tax rate is non-zero and doesn't match the tax rate of TX (Taxable) and other custom classes and log that there is a problem since we don't support that. This further adds Order.Tax Schedule to the Service Pro Order upload, and updates the Service Pro Connector to update the following values on the Tax Code:
  • Miscellaneous_PTD
  • Sales_PTD
  • Taxes_PTD
  • Miscellaneous_YTD
  • Sales_YTD
  • Taxes_YTD
  • Tax Tax Flag
  • Tax Freight Flag
  • Tax Miscellaneous Flag
Fixed
11870445 - Pickup Type On UPS API Call Raising Freight Price
Removing the Pickup Type code on our API fixed this.
Fixed
11871217 - Customer Service Order View Showing Incorrect Field For Tracking Number Freight
Two issues fixed in this branch:
  • Total Charge on the Record Shipment functionality was being saved to the Total_Cost field on the AR Shipping Transaction File table. Inexplicably, this field is actually where we store Declared Value. This screen was fixed to save it to the correct field, Cost on that same table.
  • The tracking number section on the Customer Service Order view was displaying the Total_Cost field from the AR Shipping Transaction File table as if it was the freight amount. This column was renamed Freight on the Customer Service Order view and now displays the Ship_Cost field.
Fixed
11871836 - Default Customer Type Setting Ignored
In site settings under Customer Defaults, there is an option to set Customer Type that will be set for new customers; the system was not honoring that.
Better
11872155 - Quick Cart Availability Is Controlled By Return Locations But It Isn't Always Obvious Why A Location Isn't Being Used
Improved logging for why a specific location is being used when asking for quantity available through GraphQL.
Fixed
11872270 - Cart Returning Incorrect ATP And Logging Not Giving Explanation
When using the quick cart with ATP functionality unhidden, one date was provided. When this item is added to the regular cart for checkout, a different date (five days later) was shown and there was nothing in logging to explain why this date is different. This boiled down to one location calculating when it could ship, and the other calculating when the customer would receive the item.

Back to Top

Bug Fixes - 21.0.33 - Released 8 January 2024

This build has the following bug fixes implemented: 
Fixed
8890145 - Sort Order Not Correct On Paged Categories
When a categories page has enough sub-categories under it to cause pagination, the sort order set in Site Settings was not displaying in the correct order.
Fixed
8938258 - No Way to Select Authored By On MVC Web Category Edit
Previous versions of the software included the 'Authored By' capability on web pages, but this was accidentally dropped in the transition to using MVC.
Fixed
10238344 - MVC Web Page Editor Missing Sort Method DDL
Similar to 8938258 above, previous versions of the software included the capability to set both the Sort Order and Sort Method on a page, but this was accidentally dropped in the transition to using MVC.
Better
11868279 - Page Not Found Should Log Which Page Is Not Found
This update adds level 4 logging that identifies what URL could not be found as well as recording a page hit for the not found URL with the page hit type set to Not Found (19).
Better
11868336 - Shopify Connector Error Turned Into Warning
Downgraded an upload error when using the Shopify connector sub-system so the entire upload would not come to an abrupt, crashing halt.
Fixed
11868393 - Item Data To Upload Button Is Missing From Interface
When choosing "Some" for what item master data to upload on a Shopify connector, there is supposed to be a button appearing in the interface to let the user choose which item data gets uploaded to Shopify. This button seemed to be missing, but was actually hidden and could be seen if the form was maximized. We adjusted the software so the button is now always visible.
Better
11868975 - Imports Run Under The Anonymous User's Permission Instead of Admin
Items can be set to have specific permissions but when an Admin user logged in and attempted to update these items via the Import functionality, the system was returning an error and displaying the anonymous user ID. We changed to use Admin user when importing.
Fixed
11870719 - Customer and Order Property Triggers Don't Always Work Correctly
A bug was introduced into the software in the 11868271 Create Customer And Order Property Triggers For Order Rules which was added 21.0.26 New Features. This fixes that.
Fixed
11870961 - Customer Property Triggers Have ORE When Not Logged In
When having a customer property trigger for a Note against a Macola Progression environment, an object reference error happened when attempting to login.
Better
11870999 - Support Shopify API 2023-07
Shopify only supports APIs for a year, so as of this build, we updated the BirdDog Connector Sub-System for Shopify to use the Shopify API 2023-07.

Back to Top

Bug Fixes - 21.0.26 - Released 30 November 2023

This branch has the following features implemented:
Fixed
11865665 - Shopify Bug Uploading Invoices
When uploading a Invoice from BirdDog to Shopify, we were getting an error that suggested the Invoices in BD do not match the info in Shopify.
Better
11865769 - Updated the Shopify Connector to Use API Version 2023-01
Shopify only supports APIs for a year, so as of this build, we updated the BirdDog Connector Sub-System for Shopify to use the Shopify API 2023-01.
Fixed
11867053 - Sage 100 Customer Telephone Number Too Short
Sage 100 allows telephone numbers to be 20 characters and extensions to be 6. Increased the field lengths for this.
Fixed
11867233 - Invalid Freight Account Shows Logs Error As Invalid Ship Via
This was an odd case where a ship-via code referenced a general ledger code that did not exist; in our default UI, BirdDog does not allow this as it is "illegal", but in some hosted Ecommerce environments or connector scenarios where the data isn't quite right does allow this scenario.
Fixed
11868351 - Order Rules Aren't Undoing Properly
If generating a cart that matches the order rule criteria and then the trigger was changed, the cart was not removing the effect. So, for example, if you had a rule that gives 10% off orders for people who are shipping to the state of Oklahoma and have OK at the state, you would see the 10% off, but if you changed the ship-to to Texas, you would still see the 10% off.

Back to Top

New Features

This branch has the following features implemented: 
Better
11858421 - Add Support For Sage 100 Batch Entry Being Enabled For Deposits
This makes several changes with how we handle this process with regard to Sage 100 sub-connector system. Our previous code allowed deposits to be processed, but did not anticipate the batch entry functionality being enabled on Sage, which caused no small amount of trouble when it did. This resolves that.
New
11860377 - Add Support for Shopify Variant items
Prior to this enhancement, we did not support this functionality with the Shopify Connector. This enhancement adds support for uploading variant data to items that already exist on Shopify. For this to work you must manually create an Item linkage with the appropriate values. See Special Instructions: Using Variant Items With Shopify for further information.
New
11862259 - Implementation of the Dynamic Image Optimization (DIO) System
This adds auto-sizing support to Ecommerce and is one of the reasons for the point release as it requires an update to the website install process, specifically the installation of ImageMagick on the webserver. In site settings, you establish a default width and height for Small, Medium and Large images; all such images will be resized accordingly as webp formatting. This does nothing to the actual original image; the webp images are the only ones actually affected. See here for further documentation.
Better
11864406 - Sage Connector Slow To Move Items
Significantly changed how we upload Items, Sales Orders, and Invoices while using the Sage 100 sub-connector system.
  • Fixed an issue with how default values (ie. g/l accounts, tax schedules, countries, etc.) are downloaded and the connector settings are validated to remove the item master being downloaded twice
  • Fixed an error in the item extended description lookup that was causing too much data to be returned.
  • Updated the Sage 100 connector to use the BirdDog Greatest Seen Time change tracking system per table. This will have the effect of keeping an error in one table from causing all other tables to be downloaded on the next run
New
11864934 - Added New Event: GuestOrderDownloadGetCustomerNo
This event adds the ability to assign different guest customer numbers to guest orders.
Better
11865830 - Broken Cus_No Formatting When Division Number is Missing on Customer Created Outside of Sage
This changes our handling of Sage 100 customers. Prior to this build, you always saw the division and the customer number had a maximum size of 23 (##-####################) as that was a default system settings used. However, this isn't always the case in Sage 100 and the formatting is controlled by two A/R settings at Sage 100 | Accounts Receivable | Setup | Accounts Receivable Options | Main. There can be found two options, one for Accounts Receivable Divisions, which has two sub-options of Disable (where Divisions aren't present at all) and Enabled (where they are), and Allow Entry of Expanded Customer Numbers, which also has two sub-options of Disabled (where customer numbers have a max length of 7) and Enabled (where customer numbers have a max length of 20). With this update, if you don't have Allow Entry of Expanded Customer Numbers enabled, we will drop the cus_no max field length to 10 (##-#######). Additionally, if you don't have Accounts Receivable Divisions enabled, then the system will display customer numbers without the leading division. We will continue to record them in the database with the division. All of this is to bring us more in line with the way Sage 100 works.
New
11866858 - Add Support For Webcategory Grid Fields
Add a new webcategory property named grid fields on the fields tab. This field will allow for page layouts where the user can control what item fields display in the gird. Also created a default grid field data based upon the first item in the webcategory using any non-blank fields.
Better
11868054 - Update Create User From Customer Process
This process was very old and was previously an Enterprise for Windows process. This turned that process into a job, following current best practices, and removed both the Enterprise for Windows and Enterprise UI data. Instructions for use are built-into the job.
New
11868271 - Create Customer And Order Property Triggers For Order Rules
Before this enhancement, we had a handful of individual triggers for a few customer and sales order fields. This enhancement creates a Customer and Order Property trigger that supports all properties. The old triggers are left for backward compatibility but will be removed in future versions.
Better
11868872 - Update Capture Posted Invoice Job
This changes the service data format on the Capture Posted Invoices job by altering the Starting Date from a "look back" date to an "add days to today" date format, the net result of that being if you want to go back a week, you use -7 not 7. Such a change is one of the reasons for point release. While making this change, we also updated this process to use our worker process system so it now supports adding an Email to notify and a verbosity setting.

Back to Top

Reason for Point Release

This point increase (v20 to v21) was principally caused by 11864406, which updates how upload Items, Sales Orders, and Invoices when using the Sage 100 sub-connector system. Three other projects also necessitated a point increase: 11865830, which changed how we handle Sage 100 customers and no longer added the division number if Sage was setup to not do so; 11867053, which increased some field lengths to allow for longer telephone numbers and extensions; and 11868872, which altered how we handle the Capture Posted Invoice job.

Back to Top

System Requirements Version 21

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

ImageMagick must be installed on your web server.

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 10 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 Edge; as Internet Explorer was deprecated, we no longer support it
  • 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 Edge; as Internet Explorer was deprecated, we no longer support it
  • Mozilla Firefox version 10 or later
  • Apple Safari version 5 or later
  • Google Chrome version 17 or later

Back to Top

Receive your free product tour! Need Help? Have Questions?

Industries

Find out how BirdDog Enterprise fits your niche!