Bug Fixes - 25.3.47 - Released 16 December 2024

The system was rendering the page code as About-US when it should have been https://www.mysite.com/About-Us. The Home page code should have been https://www.mysite.com (canonical URL won't render the page code when the page code matches the home page code from site settings).

This enhancement adds type-ahead search to the Entity Search Layout (Categories41).

Greatly enhanced the logging for QuickBooks Desktop. This allows us to more easily troubleshoot any unexpected errors or slowdowns on the connector run.

Corrected some minor typos.

We were observing customers returning Invalid Location even though the locations were in fact valid. This was ultimately determined to be due to Site Settings | Customer Service | Locations not having been configured properly. We updated the Default Location dropdown list (and any location DDL that has the area set to customer service) to use all locations if nothing has been configured in Site Settings | Customer Service | Locations and log what happened. We also fixed the customer diplay issues for locations as well.

Since the early days of BirdDog, we have had a Short Description field that defaults from item descriptions 1 and 2. Historically, we defaulted this value as soon as our item object touched the record. We then used Short Description as the item's description throughout our code. This worked fine for Ecommerce customers that were maintaining the item's short description in our PIM software. However, for customers not using PIM this caused trouble because we would default short description, then they would make a change to item descriptions 1 or 2, and this change would not be reflected on any of our screens (since we were using short description which was defaulted to the original value). In 25.2, we removed the process of defaulting the value to fix this. However, we missed that this left the short description blank and many of the screens were still using that value. This update switches all of the screens that were using short description to use DescriptionCalculated which returns short description if it is set, otherwise it returns description (which is a combination of item descriptions 1 and 2).

Back in Version 19, we added support for Extended Descriptions for Sage 100 where we increased the capacity of the Item Index table. However, we did not make corresponding adjustments to the BirdDog Items table, so it was choking when trying to combine the two. When the item description is longer than the short description and we need to default it, we will truncate the item description down to the short description length.

This page was not handling user roles correctly.

On Enterprise, when you set a due date on a task using BRAIN and save it, you could see the due date on the task in the project grid, but when you opened the task, there is no due date set.

Similitar to 11883112 above, this page was also not handling user roles correctly.

When shipping LTL Economy or LTL Priority, we use different logic than what we use to turn smaller orders into packages. The LTL logic was broken. After fixing this, we also updated our Freight: How It Works to expose the logic used for both kinds of shipping.

We map customer.search name to customer.name in QuickBooks Desktop. Customer.name in QBD is unique, so if you create two customers with identical names it blew up. We resolved that by now appending a (1) to the customer in QuickBooks for the first instance. This number increments each time you add another copy ... so stop doing that.

We have an ongoing project to add support for the Request For Quote (RFQ) process. This enhancement adds support with loading RFQ carts into the Shopping Cart (Ecommerce) or Order Entry (Customer Service) with a link like https://www.mysite.com?CartID={CartID}.

When using a web page using the Categories26b (FAQ with Sections) and clicking on the Top hyperlink, instead of being taken back to the top of this page, you were taken to the website home page instead.

If you have a system where Currency Manager is disabled in Company Setup and the currency master (CMCurCod_sql) does not exist, when searching on a website pointed at that database, the site was failing with an ugly and very technical-looking error.

This fixes a difference between how Syteline thinks by default vs how BirdDog thinks. By default, Syteline only tracks price/cost at the item level and we track it at the item/location level. Because of this, we were only updating the default item/location with the correct price/cost when downloading from Syteline. With this update, we now will update all item/locations with the item's price/cost.