Version 2019.1.1.1 (Limited Release)

This version was released to specific customers on Friday, April 26, 2019. These customers are the first to go live on the Avalara AvaTax system. This version is not currently in general release.

Minor Enhancements

9136: Avalara Integration - CertCapture

We’ve added support for Avalara CertCapture, but our solution has not yet been certified. We will provide more information when we receive certification.

9502: Bank Withdrawal

Modified the Positive Pay functionality so that it uses the vendor's Payee Name rather than the Vendor's Name.

Modified the "Reprice This Quote" action to use the current list price of the item(s) being repriced. Additionally, the list price stored on the respective sales line will also be refreshed at the time.

9428: Customer Quotes

Modified the Edit Shipping Information function so that the customer's address is populated in the screen by default.

9431: Customer Returns

Restocking fees are now being sent to the Avalara Sales Tax API. Additionally, we added a default Restock Tax Code to the Avalara Settings Maintenance screen.

9429: Sales Orders

Modified the Edit Shipping Information function so that the customer's address is populated in the screen by default.

9347: User Loging

We've added some new security related features to the system. We've modified the log in and out routines to trap user activity to a new table. The table is intentionally obfuscated and the data in the important columns is being encrypted. Every time a user logs in, any records that are older than 28 days are deleted. This was done to keep the storage requirements as small as possible.

We also added a new screen to the Command Center under the View menu to show the User Log. This is the only place in the system that this data is viewable. It is sorted in reverse order by default so that the latest activity is at the top. The view is intentionally a single column, partly because not all fields that are being stored will have a value depending on which activity is present on the row. Rather than grouping or sorting, the user should use the Find and/or Filter features of the grid to locate specific rows, if desired.

Finally, in order to help thwart brute force and dictionary attacks, we've added a small delay to the log in process. This shouldn't be noticeable to our users, but severely limits the speed at which those types of attacks can gain access to the system.

8649: User Maintenance

We've changed the way that two tags work in Document Control. [User] and [UserName] have both always been tied to the user's user name setting. That is the same setting that is used to log into Acclamare when using user name and password instead of Windows Identity. For sites that utilize that login method, the user name cannot contain any spaces. That can lead to situation in which these tags lead to unintended messages. We've decided to change these tags to reference the user's Email Address Name instead. That name can contain spaces. When the [User] or [UserName] tags are encountered, Acclamare will use the user's Email Address Name if one exists. If the user does not have an Email Address Name assigned, Acclamare will continue to use their User Name instead.

9432: Vendor Maintenance

Address validation is now available for the vendor's Payee Address.

Bug Fixes

9406: All Screens

Corrected an unhandled exception that could occur when opening a window that had a bad setting in its customization file. The bad setting was related to the window's position and may have been caused by the user having arranged the window so that some, or most, of the it was outside of the screen bounds.

9493: Avalara Settings Maintenance

Corrected an unhandled exception that could occur while using the Mass Validate Addresses feature. The error message coming from Avalara states that "You must provide either a valid postal code, line1 + city + region, or line1 + postal code." This issue obviously occurred if the address did not contain enough information for Avalara to attempt to validate it. Acclamare is now trapping this error. When using Mass Validation, the customer will effectively be skipped and their address will remain "Unvalidated". When using the feature within the client, the user will be shown a nicer error message that explains the problem.

9430: Customer Credits

Corrected an issue that was sending an incorrect freight value to the Avalara Sales Tax API.

9466: Customer File Maintenance

Corrected a cosmetic issue that occurred with the Residence flag. The flag has been removed from the Shipping/Billing Information area to the Shipping Address area.

9446: Kit Disassembly

Corrected an issue that caused kit related values in usage history to be incorrect when a kit was disassembled for a quantity of greater than one. If large enough, the incorrect values could cause additional issues during reorder control calculations which could then lead to the item being assigned a lower class rank that was correct.

9434: Promotion Maintenance

Corrected an unhandled exception that occurred when using the Add Items action and providing a value for the Manufacturer filter.

9086: Purchase Order

Corrected an issue that could cause the cost to be $0 when the user changed the quantity on the line and the vendor item had a Quantity UM that was greater than the base item's SKU and Quantity UMs and the vendor item contained bracketed costing that started with a bracket that had a quantity that matched the vendor item Quantity UM.

9306: Purchase Order Receiving

Corrected an issue that could cause a special order detail to have a negative backorder quantity when an excess quantity was received and the user chose to send the excess to stock instead of to the sales order document.

9409: Rework Order Receiving

Corrected an issue that set the committed quantity to an incorrect value if the incoming item was only partially received.

9465: Sales Orders

Corrected an error that occurred when the user toggled the Residence flag on a one-time shipping address.

9477: Sales Orders

Corrected an issue that prevented taxes from being recalculated if the only thing the user changed was the Taxable flag at the line level.

9340: Vendor Credits

Corrected three cosmetic issues on this screen.

The Amount field was displaying a negative value immediately after being loaded in from a search. If the user moused over or clicked on the field, the value was then correctly displayed as a positive number. The value will now always be shown correctly.
The Open button was not on the toolbar by default, so it has been added. This will not impact any current customizations, but if customizations are reset, or a new user opens the screen, the button will now be there.
Modified the search screen so that the Amount and Current Balance will be displayed as positive numbers.

Wiki