Bug Fixes: Version 9.8.7.636 - Released 6 November 2018

When you posted an order created in Macola using Accounting | Process Orders that has a kit item on the order, the components for the kit were issued at 1/100 of their actual quantity. Example: if the kit component issued a quantity of 5, Process Orders issued instead 0.05. This worked fine if the order was placed in Birddog or if the order was posted using Macola.

Field Values were erroneously set to case sensitive, so a value of "red" (for example) did not match a field value of "Red" during the import. In such a scenario now, the import will ignore case providing the data itself matches.

The Order Rule Result "Percentage Off' wasn't getting updated if you added an item to the cart after the Special Code is entered. Now, it updates every time the cart is updated.

On BRAIN/ContactForm.aspx, the Body of Contact | Notes did not get saved when you clicked Save.

Orders created and edited in Birddog software were not writing entries properly to the database.

When an quote was converted to an order using BirdDog Enterprise, the process was not properly removing the quote so both it and the order remained in the system.

Saving an edited order could delete the credit card expiration date in cicmpy if the customer CC info was edited in Macola while the order was open. This was a case of 2 things open at the same time and they were stepping on each other.

Added error handling on a number of the available buttons to catch strange exceptions.

Added a label to the page.

Tweaked the visuals for this popup so it doesn't look as bad.

Edited to improve clarity.

A customization point that existed in prior versions had been removed, added back in this release.

This table was not properly syncing which affected how orders were being handled.

Previously, you were unable to add a redirect page if the "Code" was over 50 characters. We have significantly increased that limit.

The default address (the one created when creating a new customer) was showing in the Checkout page Saved Address DDL as a blank. When you clicked on another saved address, the ship-to info changed to the one selected, however, if you then clicked the 'blank' saved address, nothing happened.

Customers with just the SaaS / Subcription license did not have access to Enterprise for Windows | Processes | Data Scrubbing items, but should have.

When importing a web category, you can use either the intended layout name or its ID (which will be a GUID.) Prior to this, the ID was the only one that would work.

The ItemForm.aspx page is determining In Stock status by looking at the item's Default Location and not the location determined by the parameters set for the item / customer. The CartForm.aspx page shows correctly based on the quantity for the location that is determined to be used for the order.

Added tooltip.

On the Checkout page, the "Phone" label & text box were located in the "Shipping Address" section. The phone number here was the "Ordered By" number, not the ship-to number so it needed to be moved to the "Your Information" section (right under "Email Address").

Software was throwing an Incorrect Syntax error but wasn't actually reporting the bad query that was the actual problem. This happened only in very specific situations with equally specific data, but we tweaked the coding to handle this kind of scenario better.

Open Orders was rating freight, which was problematic if your active customer had a very large number of Orders.

The Authorize.net merchant service was not handing the error message back correctly, so we forced the code to handle this scenario better.

Error due to customer specific data fixed.

When you run "Print Pick Tickets" in Enterprise for Windows, it was adding to the item's allocations in iminvloc_sql for every item picked (should remain the same). This was throwing off allocations every time Print Pick Tickets was run.

Saved Credit Cards that were missing address info caused the order Bill To info to blank out which resulted in the order Bill To changing to match the saved card's address info.

Tax on freight was causing order posting to throw an "Out of Balance" error when tax was from a Tax Schedule.

Orders posted using Birddog were setting the selection code to "X" (should be "Z") and not entering info in four specific fields in one table.

Orders were not sending all order confirmation emails. We discovered that some orders were throwing errors under the hood and the system was not handling them gracefully.

The "From" address for Password Recovery emails WAs using the "Default Email Address" and not the "Password Recovery Mail From" address in Site Settings>Email tab.

If the Process End of Day job was set to 'noactualprinting' (which was added in previous versions), it was throwing an error instead of completing the job.

"Allow Partial Shipments" was on Site Settings | Ecommerce | Other but this is a Customer default and needed to be moved to that tab below "Allow Back Orders".

If you do not have a USPS freight account setup, when you click on Standardize Address on a BRAIN contact, the site crashed. Now it gives you a message telling you it can't do this.

While editing a field in System Management, clicking Delete simply did it without asking for confirmation.

This table field was limited to 30 characters, which was resulting in an error during checkout if the transaction had more characters than that.

Enterprise for Windows was crashing when attempting to use this search function.

In Customer Service>Order Entry, when you entered a "Coupon Code" (from an Order Rule), you received an "Invalid Coupon Code" message on the page. The order rule worked fine in ecommerce.

Error due to customer specific data fixed.

Error due to customer specific data fixed.

Orders were getting created with "Ship Complete" as FALSE even though they marked TRUE in Site Settings.

When you converted a Quote to an Order, the "Ship Complete" box gets unchecked.

Label typo.

There were two problems with this: First, the import was trying to read the header line, and not skipping it and starting on line 2. Second, if the first column (Vendor#) was blank, the import was not creating a new Vendor with a system assigned vendor number. Instead, it shifted every column over to the left by one and then threw an error because the values for the columns didn't match the schema.

When clicking on Forgot Password from the Cart login, the link received via email was bad. If you went directly to Login and tried it that way, however, it worked fine.

Attempting to reviewing a customer that has a number with an apostrophe was causing a site crash.

The error message Enterprise for Windows was returning for a bad address failed to identify exactly what address was wrong.

Using Enterprise for Windows, the "Interface Shipping" section of the "Process End of Day" was not "Selecting" the order or adding the freight amount in the proper table to the order.

We updated how the CVV code gets sent to Auth.Net to fix this error message.

A user logging into Enteprrise for Windows without any roles assigned got a confusing and far too technical error message. Now it tells you what is actually wrong in non-developer English.

Making a change to an existing code located at Maintain | Freight | Pay Codes was causing the program to error out.

When you troed search for an item in Item Edit, you got a spinner that never goes away and no results ever appeared.

On the search form, keyword search was not filtering results to only items that were in an audience.

This Order Rule Result only worked when a specific trigger was also included in the rule.

If an ampersand ("&") is in the customer number, credit cards simply would not process. This was only the case in Customer Service Order Entry.

Added support for Bins when selecting and posting.

Enterprise for Windows was not properly recognizing this license so those who had it could not use it.

An unexpected value in the Edi_fg column on the order and invoice header would cause errors. Now it no longer causes a system crash.

When an order was placed in ecommerce, a new saved ship-to was being created with the shipping address that was used even if it is the customer's default shipping address.

This happened only with the O/E Setup Profit Center Usage was set to O=Ord Pft Ctr and was causing some issues with accounting.

The system was allowing you enter a duplicate "Code" in Freight Pay Codes. This must be a unique code.

When you go to Manufacturing>Work Orders and click on an order number, you get "Page Not Found".

We weren't sending Exempt on the transaction when that flag is checked in an order.

Fixed scenarios where data in IMInvTrx_sql was not being formatted correctly.

If you have an order rule using a coupon code and apply the code before logging in, it worked fine. This is also true if you login first. However, if you apply the coupon and then login, the discount goes away.

Fixed error where multiple records per invoice could get into BDInvoiceSupport.

Updated end of day process to not error when seeing quotes unexpectedly.

Canadian tax laws are complicated and thus require a tax schedule setup in a specific way. If this schedule does not exist, the software now alerts you to this fact instead of displaying a confusing error message.

We were missing the all important Quantity field on our Bill of Materials import.

When viewing an order in order history, if the item (in line items) does not have a small image, then the first column (which displays the image) displayed garbage instead of being blank.

Fixed scenarios where data in IMInvTrx_sql was not being formatted correctly.

When a company is not licensed for customer service but the module is licensed, attempts to use it resulted in a site error.

This job was not working properly.

On the invoice report, the "Total" & "Balance Due" were not always the same (with Amount Received = 0). For example: Total = 206319.38 & Balance Due = 206319.40. This bug fix requires an update to Invoice.rpt and an customized invoice report that you have.

Fixed error where multiple records per invoice could get into BDInvoiceSupport.

The BirdDog point-of-sale software was not properly reading a printer-related setting when finalizing a sales order.

Credit Card orders were writing to oecshfil_sql.trx_type as 'X' instead of 'C' like they should which was causing problems in Macola as the order needs to come in as Type = Bank Statement otherwise you only get a total with no details to be able to reconcile.

When using a non-admin User in Enterprise for Windows, this error was being thrown when attempting to import G/L Transactions. Admin users worked fine and this did not always happen on every database.

The search filter "Only Lines with Qty Remaining" for Manufacturing>Work Orders did not work. You could set it to "TRUE" and still get work orders with Qty Remaining = 0.

When you add a new customer type, the "G/L Accounts" tab is not loading the default account info from the proper table.

When running Commit Sales Tax, the software did not tell you how many invoices failed to report to Avalara correctly.

When you went to the Checkout page, the system should default to the first Ship Via that rates correctly but did not in previous versions. However, if you went to the checkout page and then back to the cart and then back to the checkout page, it defaulted correctly.

9.8.6 builds of the website were, in certain specific scenarios, causing the application pool in IIS to crash.

When using Enterprise for Windows>Transactions>Invoicing>Process Invoices, the Balance Due on the Invoice Report was being calculated incorrectly.

In Maintain>Items..., the Main Setup tab showed as "disabled" and would not allow editing of info on that page.

One of our wires was crossed and as a result, Enterprise for Windows stated that the engine was not supported when attempting to access the Connector Accounts using a Macola ES database.

Error due to customer specific data fixed.

Fixed the page.

Navigating to this menu item was erroring out the program.

These processes were erroring out in previous builds.

Obsolete reports have been removed.

Making a change to an existing code located at Maintain | Freight | Pay Codes was causing the program to error out.

This rule trigger was not working correctly.