Version 23

×

23.1

23.0

System Requirements Version 23

23.1

Bug Fixes - 23.1.36 - Released 26 August 2024

This build has no version specific bugs that need to be reported, but has cumulative fixes from prior versions merged into it.

Back to Top

Bug Fixes - 23.1.34 - Released 27 June 2024

This build has no version specific bugs that need to be reported, but has cumulative fixes from prior versions merged into it.

Back to Top

Bug Fixes - 23.1.33 - Released 4 June 2024

This build has the following bug fixes implemented: 
Fixed
11874229 - Item Image Carousel Isn't Using DIO Images
When the image carousel for items is set up so multiple images will show, the system was not pulling from the correct place.
Fixed
11875094 - Feature Items Can't Be Purchased
In earlier versions, we added a test to see if an item's price is zero and, if so, disallowing purchasing unless you have the employee role. This was a problem until this build for Feature Items since they evaluate to zero price until options are chosen.
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 - 23.1.23 - Released 27 April 2024

This build has the following bug fixes implemented:
Better
11861630 - Support Using Tax Schedules in AvaTax
We have supported tax codes in AvaTax for ages, operating on the presumption that since Avalara handles all of that, we didn't need to worry about tax schedules. This adds tax schedule support.
Better
11867614 - Update Customer Portal License
Made a number of alterations to this license.
  • It now includes Website and Intranet builder when purchased.
  • Added customer and item edit to the System Management page and don't require anything but an Enterprise Named User license to use.
  • Removed support for Order Cancellation Reason.
Fixed
11873129 - HTML Showing Up In Search Results
The search page displays a snipped version of a page's Long Description, and was erroneously displaying fragments of HTML on that page when it was not supposed to.
Fixed
11873848 - Connector Notification Email Field Not Handling 100+ Characters
Observed in the ServicePro Connector, but ultimately affects all connectors. While it appeared that exceeding the 100 character limit in the Notification Email field on a connector was the problem, the actual issue was that the system wasn't supporting a list of emails at all, instead seeing the string as a single email address. In addition to resolving that, we also increased the connector account notification field to 4,000 characters. If you need more than that, you should really consider creating an alias for all of those addresses in your email server.
Fixed
11873903 - Error When Entering Cash Receipts
An ugly error was happening when attempting to add a cash receipt using Enterprise. The root cause turned out to be the customer search not returning correct data and the cash receipt dialog was not handling a customer number being blank.
Fixed
11874342 - BRAIN Campaign Include/Exclude Groups Not Working Correctly When On The Same Contact
If an organization had both of these groups when a campaign was generated, the organization was correctly being left out of the list due to Exclude; any contacts under that organization, however, were still included.
Better
11874541 - Removed Support For Order Cancellation Reason
Prior to this build, when you were deleting an existing customer order or quote in Customer Service, you were required to select a reason for this delete, which added an extra few steps to the process. Due to frequent request, we have removed that functionality.
Fixed
11874870 - Importing Inspection Item Overwriting Hierarchy And Changing Published Status
When you try and import an Inspection item to ServicePro, it overwrote the inspection heirarchy and changed the published status.
Better
11875448 - Order Entry Not Displaying Freight Errors Correctly
When trying to rate freight from inventory locations that did not have actual addresses, the order entry system was returning a confusing and less than helpful error. Now it states: "Ship From information incomplete, Location {Location Code} most likely missing address information, instead you receive Ship Via {Ship Via Code} not yet rated."

Back to Top

Bug Fixes - 23.1.7 - Released 1 March 2024

This build has the following bug fixes implemented: 
Better
11868922 - Added Requested Quote To Shipment Quote View Screen In Enterprise for Windows
We were observing some unexplained differences between the freight quote that we returned and what UPS returned on their website but could not identify exactly what was going on, so we added this extra tab with the request at Enterprise for Windows | View | Freight | Rate Order. This is principally intended to be a troubleshooting tool.

Back to Top

New Features

This branch has the following features implemented: 
New
11872310 - Add Default Thank You For Your Submission Page
This adds a new page that our revised Categories30 page redirects you to when you click on submit.
New
11871841 - Create Request Form Layout
This replaces the old email-based Info Request form (Categories27) with a multipurpose, highly-configurable Entity and/or email-based form. When so configured, it will generate its own Entity support tables and Fields to store form submissions. Submissions can be emailed with a hard-coded template or use the system's Email Templates.
Better
11873144 - Add Images to Search Results
This is custom behavior and requires web development to implement. When showing images on the category (Site) results on the search page, going to "vew more results" and returning back no longer causes the images to disappear.

Back to Top

23.0

Bug Fixes - 23.0.30 - Released 27 April 2024

This build has the following bug fixes implemented: 
Fixed
11871443 - Change Tracking Doesn't Handle Multiple Records In BD_Audit_BDOrderSupport For A Single Order
Observed in the ServicePro Connector. BD_Audit_BDOrderSupport uses BDOrderSupport.ID as the key. This allows for scenarios where the same Ord_Type/Ord_No can have a different ID.
Fixed
11874145 - Item.Tags Object Reference Error When Viewing An Item
When attempting to view an item in Enterprise, the system was crashing and throwing a object reference error. This was caused by 11869703, which was added in 23.0.

Back to Top

Bug Fixes - 23.0.26 - Released 19 February 2024

This build has the following bug fixes implemented: 
Fixed
11870692 - Cannot Import Sales Order Without Lines
When using the Import Sales Order functionality, the system would not allow you to import an order without lines.
Better
11870878 - Order.Job Number Length Needs To Be Increased In BirdDog Engine-Type Databases
Altered field lengths in a number of tables to fit standards for supported ERPs. This is one of the reasons for the point release.
Better
11870886 - Invalid Equipment Code For Valid Equipment On Order Downloads
We were seeing errors indicating that an order downloaded using the Service Pro connector was using invalid Equipment when that was not the case. Resolved this error.
Better
11871893 - Add Equipment Validation Back to Order Imports
In 22.0.33, we released major enhancements to the Service Pro Exchange system which included an import to support Equipment on Service Pro. We initially removed all equipment validation to allow for historical orders to be downloaded without issue. Before, orders with equipment that had since been moved from the order's site would throw an error on download. We removed this validation, as well as validation going upwards. This project adds that validation back so an import cannot accidentally generate an order for Customer X with Customer Y's Equipment.
Fixed
11871894 - Order Line Import Not Allowing For Multiple Line Imports
When using the Import Sales Order functionality, the system would allow you to import an order with a single order line, but not multiples.
Better
11871911 - Service Pro Connector Not Reporting Warning When Not Uploading Because Order Has A Completion Date
When using the Service Pro connector, attempts to upload line items to an order that has been Completed now report a clear warning: Work order:{Order.Ord_No} exists on Service Pro and has a completed date of:{raw.Single.Item("CompletedDateTime")}, order will not be uploaded.
Better
11872016 - Increase UOM Length To 10 For Microsoft AX
Altered field lengths in a number of tables to better support this ERP. This is one of the reasons for the point release.
Better
11872302 - Add Culture Name Back To Site Settings
Culture setting was accidentally dropped from older versions of Site Settings. We added it back with this.
Fixed
11872505 - Order Support ShipVia Length Not Long Enough
Increased this field length to better support the Service Pro connector. This is one of the reasons for the point release.
Fixed
11872548 - Service Pro Connector Does Not Handle States With Spaces In The Name
While something of an outlier, we discovered that a state or province with a space in the name was messing up the city/state/zip parser in our Service Pro connector

Back to Top

New Features

This branch has the following features implemented: 
Better
11860195 - Write Freight to the Sage 100 Sales Order
This adds support for upload Sales Order.Freight to Sage 100. Prior to this we were downloading it from Sage 100. Note: for this to work, Sage 100 must be configured correctly by going to Sage 100 | Sales Order | Setup | Sales Order Options | Entry | Use Shipping Code to Calculate Freight and selecting No. If Sage 100 is configured to use a different option, it will disregard any freight amount we upload.
Better
11868550 - Run Connector Job Won't Restart When Prematurely Ended
While technically a bug fix, the underlying code fix was sufficiently complicated that we consider this a new feature. Job Master now thinks in terms of Jobs instead of Job Types. The run logic now makes a list of all jobs that should run, puts them in a list of jobs to run, and then loops through the list. Before running each job, it validates that it should still run (because now another process could have ran it), sets the last run time, and then starts the job. With the addition of the processID in BDServices, Job Master can now check that a process is running BD jobs and, if it is not, mark it ended. This update has schema updates to our Services Tracking table, which caused the version point increase.
Better
11869552 - Add Ordered By Fields To Sales Order Import
This moves the order by fields from BDCarts to BDOrderSupport when viewing sales orders and invoices from Customer Service (previously they were pulled from the cart even after the order was placed). This requires a data conversion - see this link for additional information.
New
11869703 - Add Tag Support
This updates and makes more generic the work started in 11862080 Create Tagged Categories and Items Page Layout which was released in 20.1.49. Changes made are:
  • Added Tags to webcategory and item editor
  • Updated Categories39 to use standard tags property unless overwritten by on-page customizations
  • Updated Categories39 to allow data to come from URL
  • Update web category and item import with tags
  • Added default tag display to ItemForm.aspx and Categories.aspx
Better
11871443 - Change Tracking Doesn't Handle Multiple Records In Order Support Audit Table For A Single Order
While normally there is only one audit record in BD_Audit_BDOrderSupport, there are scenarios involving deletes and re-adds of the same order number that can create multiple records. This fix handles those scenarios correctly.
Better
11871787 - Add Timeout Setting For Long Running SQL Queries
Once any process has used SQL change tracking, there will be a new setting created named SQLTimeoutLong with a default value of 300 (seconds, so 5 minutes). This value can be edited to change the value used.
Better
11872362 - Add Serial/Lot Flag and ES User Defined Field 6-7 to Item Import
The imitmidx_sql user_fld_6 and user_fld_7 fields only exist in ES. To keep the item import consistent between engine types, we added these fields to the BD Items table for Macola Pro and BirdDog Engine databases. This caused a minor schema change and is one of the reasons for the point release.

Back to Top

Upgrade Notes

11869552 adds a field to the sales order import. This build will automatically update the schema so nothing will be needed. However, if you are working on an environment with a staging site while production is on an older version, the older version will continue to write/update data in the wrong place. Once staging is taken live, you will need to manually run the data conversion again:

update BDOrderSupport
set Ordered_ByID=c.Ordered_ByID
,Ordered_ByName=c.Ordered_ByName
,Ordered_ByPhone=c.Ordered_ByPhone
,Ordered_ByPhoneExt=c.Ordered_ByPhoneExt
from BDCarts c
join BDOrderSupport os on os.Ord_Type=c.OrdType and os.Ord_No=c.OrdNo
where c.Ordered_ByID<>'00000000-0000-0000-0000-000000000000'
or isnull(c.Ordered_ByName,'')<>''
or isnull(c.Ordered_ByPhone,'')<>''
or isnull(c.Ordered_ByPhoneExt,'')<>''

Back to Top

Reason for Point Release

This point increase (v22 to v23) was primairly caused by major changes to the Job Master system. More information can be found by reviewing the appropriate information on the New Features page.

There were also a number of other schema alterations that prompted this, specifically: Increased field lengths for Order.Job Number for several ERPS; increased the UOM field length to 10 in a number of tables to better support Microsoft AX; and moved the order by fields from BDCarts to BDOrderSupport.

Back to Top

System Requirements Version 23

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 - a good rule of thumb to follow for Windows versions: if Microsoft is no longer supporting it, we probably aren't either.
  • 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
  • Microsoft Windows Server 2022

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
  • Microsoft SQL Server 2022, any edition

Full-Text Search needs to be installed on your SQL Server for our software to function correctly. And as with the Windows note above, a good rule of thumb to follow for MS SQL Server versions: if Microsoft is no longer supporting it, we probably aren't either.

Back to Top

Work Station Requirements

  • 2gb of RAM
  • 2GHZ or better CPU
  • High-speed internet
  • Windows 10 or later - a good rule of thumb to follow for Windows versions: if Microsoft is no longer supporting it, we're probably not either.
  • 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 the latest version of one of the following browsers:

  • MS Edge; as IE was deprecated by Microsoft, we no longer support it.
  • Mozilla Firefox (still our favorite!)
  • Apple Safari
  • Google Chrome
Web-browser Requirements for Enterprise
Our ERP system can be accessed by any device with the latest version of one of the following browsers::
  • MS Edge; as IE was deprecated by Microsoft, we no longer support it.
  • Mozilla Firefox (still our favorite!)
  • Apple Safari
  • Google Chrome

Back to Top

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

Industries

Find out how BirdDog Enterprise fits your niche!