Account Maintenance

There are now two (2) separate options for "no prices at POS" for customer accounts. One controls whether prices will be printed during Point of Sale processing for transactions where a "no prices" style is available. The second (bottom) option determines whether Email (and Fax) documents include pricing or not. For example, this would allow printing without prices at time of sale while permitting the Emailed copy of the customer's invoice to include prices for the same customer. Global Modify supports the setting of these fields. The upper check box (Account Maintenance) is for printing and the bottom for Email/Fax transmission (labels will be added in a future version). Important: these settings only set the print style when printing from a transaction (Sales, Orders, etc.) and not from Documents or the document Viewer.

TSYS Cayan Card Processing

For "card on file" transactions, we are ensuring that any changes to the selected account clears the card on file information if previously set for the transaction. In addition, selected card types in Parameters no longer affect "card on file" processing if a card type is or is not selected matching the card on file record. In addition, tokenized returns (referencing an original invoice) will no longer check the list of supported card types. They will be processed regardless of whether the card type is enabled or disabled by any parameters.

When "card on file," "manual entry," or "card not present" is selected from the Context Menu on the remittance Bankcard panel on the Process (F12) form, we only allow one selection. Choosing another option will clear any previous selection for these three (3) types.

D-38519 - Mask the Card Expiry Date in all cases when building the decline receipt for a TSYS Cayan bankcard transaction. Previously AMEX (American Express) required display of the expiry date but the TSYS Cayan requirements have now changed. (12.5.19)

E-Commerce Inquiry

The E-Commerce Inquiry has been enabled for companies operating in the United Kingdom (UK).

Enhanced Item Returns

A defect was corrected that could occur when returning an item and enhanced item returns was enabled.

Folders

The Open Documents (Open Docs) folder under the Customer tab in the Point of Sale folders was not displaying any data. (12.5.18)

Payouts, Deposit Refunds (TSYS Cayan)

When refunding an order deposit that was paid by card (using the TSYS Cayan interface), and more than one deposit was involved, those deposits must be refunded individually starting with the highest deposit amount first. TSYS Cayan does not permit automatic refunds based on an original transaction token to exceed the original transaction amount. For this reason, each deposit taken must be individually refunded. Use the links associated with the customer order document to find the deposit amounts involving payment by card. If this process is followed, the refunds should allow processing without the customer's card needing to be present.

Point of Sale - Handles Exception

An issue where the number of "handles" (resources) used by the application could build up over time exceeding the limit established by Microsoft has been resolved. The handles limit would be reached at approximately 270 transactions (if the application remained open during this entire time) and would result in an application abort one the handles limit was reached. If the application were closed and re-opened before this, the handles would be released. (12.5.20)

True Value - Limited Use Coupons

An error would occur during validation if a limited use type coupon was included in a transaction along with other coupon types. This has been corrected (12.5.15). Additional fixes for limited use coupons, requiring database changes, will be included in an upcoming release.

Unit Item Maintenance

This existing utility has been added to the Point of Sale utilities menu for cases where a user may need to split or otherwise make changes to an existing unit during a sale.

A defect was corrected where an application exception could occur if the unit item's BASE measure didn't match the Code Definitions defaults for the default Each/Piece measure.

Verifone Point (Card Processing)

The item display was not clearing when using the "Shared POS" station setting and there was no change due. This has been corrected.

Adjustments (Receiving)

A new apply method has been added for Receiving type adjustments. Now, a user may set the "Method" for an adjustment code as "Percent of Stocked Total" if the adjustment code category is Receiving, and if "DO NOT AP Bill" is checked. If the adjustment code is applied to item(s) in Receipts, that adjustment code value will only be applied to stocked items. Non-stocked items will have a value of zero for that adjustment code slot.

Do it Best® Server Migration

Do It Best is changing their EDI Mailboxes to a new server. This release will automatically migrate your mailbox over to the new system when Do It Best enables if for your mailbox. The system will check hourly in your mailbox to see if Do It Best wishes you to migrate, and if so, will cause the migration to occur. Once the migration of the mailbox occurs, the branch EDI settings for the Send and Recv scripts will be changed to DIRECT as the new server needs a new connection method. MOVEit Freely® will no longer be necessary. The new ftp address for Do it Best is ftp.edi.doitbestcorp.com port 10021. Technical details: The hourly EDI routine will check hourly to see if a file exists on the Do it Best mailbox. If the file exists, it will check to see if it can connect to the new server. If it can, the migration will happen. A file is uploaded to the old mailbox and that causes the migration to occur. After a five (5) minute wait the new server will be enabled and the EDI defaults will be changed to DIRECT for send and receive scripts. A file will be uploaded to the new server indicating successful migration.

Note: If users attempt EDI processing while the mailbox is being migrated, they will see the following message: "Do it Best EDI is locked and your mailbox is being migrated to a new server. The process usually takes five (5) minutes. Please try again in a few minutes." Do It Best controls when the migration happens by placing a migration file in your mailbox.

EJD Wholesaler EDI

This release includes the new EJD (Emery-Jensen Distribution) EDI feature. Additional information and documentation will be included in a future update.

Order Entry, Build (F7), Replenishment

Due to an issue where the application would target a lower Microsoft Framework (CLR) version (2.0), the replenishment build option would sometimes error. This has been corrected. (12.5.25)

Receipts

If empty rows existed in the data grid along with a valid "unit tally" item, an application exception would be generated when choosing the "Define Unit(s)" selection from the context menu. This has been corrected.

Vendor EDI

Direct FTP operations will now retry the connection test routine up to 10 times, each attempt one (1) minute apart, before failing when running as a background process. This will prevent some issues when Internet or network issues abnormally interrupt automated EDI processing. (12.5.20)

EDI - Do it Best

Blank PO Line were not showing in the Vendor EDI summary grid when detail lines in the order data confirmation did not have a PO reference. (1.12.5.25)

EDI - True Value

The coupon load and maintenance features were not recalculating the price levels after changes to the coupon SKU price were saved. In addition, the coupon source, type, and brand name were not being set in the main (common) item record. This has been corrected. (12.5.16)

EDI - LMC and LBM Advantage

There were cases where the "batch date" on payables would be NULL (nothing) and cause an issue during AP retrieval for EDI processing. This has been corrected. (12.5.16)

When EDI processing retrieved payable invoices and multiple document (receipt) references existed on one AP Invoice (e.g. ENAP/LBM Advantage) the data grid would show two entries for each AP Invoice, one of them blank. Now it will only show one. There was a flag set that set the blank invoice number and if one of the two references were blank that flag was being set. Now the logic is if any is set the blank doc flag is false. (12.5.20)

Item Returns

For returns that are processed with a status of "Vendor Credit - Discard," we now mark the resulting receipt documents as "do not track" so that they aren't included when viewing tracking history. Receipts with document notes of "(do not track)" don't change on-hand values. In the case of a "discard," the product isn't being returned to stock. In the past, the receipt documents weren't being updated properly, so they would be listed in the tracking inquiry.

Price Updates

For applicable types of price updates, users can now add "entry" (item) notes to rows entered. If "document" notes are added, the note will be applied to any items that don't have their own "entry" notes. Once applied, the price update (or sale) notes will be shown on the resulting document with the items.

Tags & Labels

Three (3) new design elements for user-defined unit fields have been added to the label designer (Unit User Defined 1, 2, and 3). These are found on tab page 6 of the Label Design form.

Changes were made to the Unit Tag label types to properly print the item number (SKU) which is now the base SKU of the unit, not the unit's numeric tag ID. The base SKU description is printed when using the ITEM_DESCRIPTION element.

The unit's tally, used with fixed-length tally items, will wrap to additional lines when necessary. Please note: there is no need to re-size the UNIT_TALLY element in this case.

A new Import (F2) function named "Unit Item Tally" has been added for unit selection. This is only visible after selecting the "Unit Tags" radio button. Units can also be imported from a receipt document.

Transfers

Item ("entry") notes were missing on transfer documents. This has been corrected.

Unit cost on single-item unit tally items was being set to zero after unit selection. This issue has been corrected.

Build Units

The "Build Units" utility, which allows creating a new Unit from existing stock, has been enabled on the Inventory, Utilities menu. It was previously set to "not yet implemented" preventing access.

Work Orders

We have corrected an issue where the "In Progress" color indicator wasn't being applied to clipboard items.

Statements (Single File)

The single file print feature is available for use, and can be enabled by setting the "Statement-Invoice Single File" parameter (Receivables tab). When printing statements (or Email), a single file is generated containing both the statements and invoices together. This helps ensure that they will be printed together. Since the statement and invoices are combined into a single file, the statements and invoices cannot be printed to different trays. In addition, the invoices will be printed in 1-UP (full page) format ignoring any "Invoice Reprint Type" parameter if set to 2-UP or 4-UP. We are working on code to process the invoices using the 2-UP and 4-UP styles in the same print file as the statement.

Totals weren't always printing on the "remit" pages for open item statements where the "remit" style was used if a discount was involved. This has been corrected.

When using the single-file option and the statement range included some accounts that were print-only and others that were Email only, the "last account" value would not be reset causing statements to be combined together. This has been corrected. (12.5.15)

Printing using the LOCAL printer option could cause an error. In this case, we are now setting the proper defaults to prevent errors. (12.5.15)

When printing using the "single file" option, false errors were sometimes being reported due to the page count for invoices being off. (12.5.18)

An issue was introduced in 1.12.5.13 where a fix was implemented for certain optional statement pages that were missing certain totals. The printed total for net due was subtracting out the statement discount from a figure that already reflected the discount. This was an issue with the statement documents, totals were correct in the data and software areas where they are displayed. (1.12.5.24)

Billing Entry

On the Receipts (F5) dialog, a new check box labeled, "Do not update terms from PO," has been added. If checked (selected), existing terms on the invoice will not be adjusted if a receipt is selected with terms that differ. If the check box is not selected (checked), the terms will be updated to match the selected receipt.

For companies using "non-standard" General Ledger cycles, check refunds issued from Point of Sale (backroom check) were setting the wrong ledger cycle (was off by one month). This has been corrected.

Notifications

For companies using enhance item returns, a notification will be sent when items are returned and have been updated using the Item Returns utility that require further processing (would not include any returns designated as "return to stock"). Notifications will either go to the designated Payables administrator user (if set) or the system administrator (if no "payables" admin user is defined). An example notification is listed below:

No item(s) need to be returned. Copy Receipt 1705-530072 into A/P.

Schedule Payments

We have added two (2) new options to the context menu allowing users to "Select Highlighted" or "Clear Highlighted" data rows. This allows for selecting a range or randomly selected data rows for processing. Users can select sequential rows by holding down SHIFT while clicking or using the arrow keys to highlight rows in the data grid. Random rows can be selected by holding the CTRL key while clicking.

Balance Sheet

For non-standard General Ledger customers, the cycle selections were incorrect.

Income Statement

For non-standard General Ledger customers, the cycle selections were incorrect, and the selected (relative) cycle was set to one month in the future.

When running the "To Date" version of the report, the percentage value for "actual" on the Operating Income line wasn't being set (it was carrying over the same percentage as the gross margin line). This has been corrected. (12.5.17)

Post Journals

For non-standard General Ledger customers, posting wasn't being permitted in the current (oldest) open cycle. This has been corrected.

Copy Recurring Journals

For non-standard General Ledger customers, a null reference exception would occur. This has been corrected.

Load Schedule

The clipboard would become locked if more than six loads were created due to DPI Aware changes (for high resolution monitor support). This has been corrected.

Branch Setup

A message would appear when adding a new branch that the screen could not be initialized. This was caused by code attempting to remove a folder tab from the folder collection after it had previously been removed.

Device Maintenance

The Devices form (Main Menu > Maintenance > Database > Devices) has undergone a significant UI (User Interface) refresh. The appearance of the form has been updated for better organization and to allow for additional settings and features.

A new group panel has been added to the form named, "Remote Client." This has been added to support printing using either a customer's RDP (Remote Desktop Protocol) connection or a remote client application as opposed to a VPN (Virtual Private Network).

Parameters, Point of Sale, Pricing

A fix was made to the price range table. Comparison of start price and end price was being done on the string value, rather than on the decimal-converted value. As a result, some cases were missed in the process, causing task-list errors to trigger inappropriately. This has been addressed by doing a decimal value comparison rather than a string comparison. (12.5.15)

Universal Log Inquiry

Users may notice a new inquiry listed under the Maintenance area's Inquiry menu. This is currently under development and will allow inquiries for the "universal log" which records miscellaneous information for auditing purposes. This is notfully enabledin this release, but will be available with the next release.

User Maintenance

The User Maintenance (Main Menu > Maintenance > Database > User ID) form has undergone a significant UI (User Interface) refresh. The appearance of the form has been updated for better organization and to allow for additional settings and features.

Microsoft Framework CLR (Cloud Hosted)

In some cases, cloud hosted customers who were installed using the consolidated install process were pointing to an older Microsoft framework (CLR or Client Language Run-time) than would normally be used. This had to do with the location of the configuration file that indicates which CLR to use in the hosting environment. We have made changes to use the higher CLR when possible. Using the lower CLR caused issues and limitations in certain cases. (12.5.25)

DYMO Document Labels

Only one label copy was being printed regardless of the number specified by the user on the Process (F12) form. Affected various transactions. (12.5.17)

An exception could occur if a station was assigned to a DYMO printer, but no DYMO printer was installed on the PC using that station. (12.5.18)

When printing document barcode labels, multiple labels would be printed due to an issue checking the printer settings. This has been corrected. (12.5.22)

Email, Fax & Print Queue (formerly the Fax & Email Queue)

The Email, Fax & Print Queue feature available from the Maintenance area's Utilities menu and Office menu (in other application areas) has been renamed and has an added feature for use in supporting RDP (Remote Desktop Protocol) and client printing for our cloud-hosted customers (ECi Software Solutions hosting using IBM SoftLayer). Remote printing uses either remote client software or the remote desktop connection for managing printing in place of a VPN connection. This has a number of benefits including increased speed and reduced load on server resources. It also makes adding printer devices an easier process for our customers.

Email & Fax Processing

An issue with the fax queue was identified during BETA testing and has been corrected.

A number of issues generating PDF documents for Email were addressed in release 12.5.11 (not released) and release 12.5.14 (released to BETA). These were caused by changes to print handling for remote client (VPN-less) printing changes. The most recent change dealt with an issue caused by code changes that prevented a "virtual" print driver from being used in cases where services (running on the server) did not have a designated default printer. In cases where there is no default printer for the service user account, we will attempt to find a suitable alternative and if none is found, use a virtual driver instead (the virtual driver can only be used for limited types of processing such as Email). In order for services to create PDF documents for Email attachments, there must be at least one suitable printer installed and accessible by the services user. This can be the Microsoft XPS Writer which is generally installed by default.

Licensing

An issue was corrected after being identified with licensing and cloud-hosted customers using the consolidated install process where the database name wasn't being set properly on the license check request. We are now using an environment variable to retrieve the database name instead of the configuration file (which doesn't exist in the case of a consolidated install). This could cause erroneous license check errors. The proper database name should now be passed to the license check in all cases now. This issue only affected certain cloud-hosted customers.

We have extended the expiration date of this release (12.5.19) until October 4, 2017. Release 12.9.0 is expected to be available for general release in September 2017.

Printing

Code changes were made to ensure we are retrieving the correct printer paper sources and sizes. Previous code dimensioned arrays initially to the size returned from the Microsoft printer settings. Accessing this property in later code return different information in some cases. This would cause index out of range errors when compared to the previously dimensioned arrays. In particular, the problem seemed to involve using a print server. The symptom of the problem was delays in retrieving the full printer settings. (1.12.5.25)

Daily Sales

The Capital One Trade Credit (formerly BlueTarp) amount was missing from the report and has been corrected. Please note: the Capital One Trade Credit (formerly BlueTarp) amount is only shown if there is a non-zero total for the Capital One Trade Credit (formerly BlueTarp) transactions for the reporting period.