Adagio PurchaseOrders 9.2B

·    In PurchaseOrders 9.2B when adding an item on the fly while entering a PO, if the new item number had leading spaces, the ‘Unit of Measure’ and ‘Db GL Account’ fields were blank on the detail screen.

·    PDFs of PO receipts could not be viewed from the View Transactions in Adagio Ledger. The Vendor Document Number is now sent to the G/L instead of the PO Document Number to correct this.

·    If you received all items on a receipt but did not complete the receipt when prompted, then later you completed the receipt using the ‘Complete’ button on the PO’s grid, the error “Error adding record to Adagio Filter Matches, record already exists” displayed in some cases.

·    Receipt PDFs could not be viewed from receipt grids if the Vendor Document Number was longer than 8 characters.

·    The number of characters you can enter in the Vendor Document Number field was not limited to the maximum of 12.

·    When a purchase order was copied, items having a Line Discount did not have the discount on the new purchase order.

·    In PurchaseOrders 8.1C and higher, when purchase orders for the same foreign currency vendor but with different exchange rates were combined, the rate for lines added from the older purchase order was not updated.

·    In PurchaseOrders 8.1C (2013.09.13) and higher, when the ‘Check for duplicate AP documents on entry’ option in the Company Profile was off, the program checked for duplicates regardless.

·    Added Alt-A speed key to select the ‘Allocated misc.’ field on the detail screen when using manual proration of a miscellaneous charge.

Posting

·    In PurchaseOrders 9.2B, posting Receipts with Manual prorated cost doubled the allocated cost for each item.

·    If you posted an adjustment to a receipt and Day End had not be run after entering the receipt and if the Data Integrity Check was run at that point, it reported a false error. A rebuild did not correct the error but the error no longer appeared after Day End was run and no problems resulted.

·    In PurchaseOrders 8.1C (2013.05.17) and later, if you entered a receipt in an alternate unit of measure that was not the costing unit, Day End put the wrong Unit in IC Transaction History. Although the quantity was correct in IC History, this caused problems in the backdated Item Valuation and Stock Card reports in Adagio Inventory. The quantity is now always written to IC History in stocking unit. Custom reports and GridView views that use the Unit field to convert quantities may need to be adjusted.

Printing Documents

·    Fields D22 and E63 could not be dragged onto spec. They had to be selected.

·    Updated All Spec is installed. Values reported in spec codes E66 and E68 were reversed on the spec.

·    In PurchaseOrders 9.2B when ‘Allow Direct Printing of PO’s’ was enabled, if you edited an existing purchase order that had not been printed yet, posted and printed it directly after posting, the message “Error adding record to Adagio Filter Matches, record already exists.” was displayed when in fact there was no error.

·    In PurchaseOrders 9.2B, there was an error when emailing or faxing documents using the Reports | Print Documents function. There was no problem printing from this function or when emailing / faxing from the Document List.

Day End

·    In PurchaseOrders 9.2B (2016.03.10) and subsequent 9.2B Hot Fixes, when the Day End function was closed, the program stopped responding intermittently on some machines.

Reports

·    After installing Ledger 9.2B (2016.08.10) or SysUpdater (160809), temporary files created on workstations by printing reports were not deleted in some cases, although this did not cause any problems.

·    If Expected Receipt Date was blank it printed as 12/31/1899 on the Outstanding Purchase Orders report.

·    Fixes error in PurchaseOrders when printing the DayEnd Audit List report after installing Ledger 9.2B (2016.08.10) or SysUpdater (160804 and a message such as “Cannot open file \SOFTRAK\DATA\EZSEMTAB. The system cannot find the specified file.” was displayed. No other reports in PurchaseOrders or in any other module have this problem.

·    In PurchaseOrders 9.2A and higher, the Outstanding Receipt Invoice List report did not include some receipts when the ‘Vendor Doc. Date’ option was used.

·    The ReportConvertor utility displayed an error when converting custom Crystal reports created for PurchaseOrders 9.2A to PurchaseOrders 9.2B, in some cases, when the report included tables for other modules at versions prior to 9.2B. This has been corrected and the ReportConvertor installed will fix the problem for PurchaseOrders and future releases of other 9.2B modules.

Import

·    Importing a receipt for a foreign currency vendor did not update the Exchange Rate on the receipt when the rate had changed.

Miscellaneous

·    PurchaseOrders now renders dialogs properly on Ultra High Resolution displays when the font size is anything other than 100% of normal on Windows 8.1 or higher. All Adagio releases dated in September 2016 and later have this problem fixed. For releases prior to this date, the utility program SetScreenForAdagio.EXE is installed in the \Softrak\System folder to correct the problem.

·    The email password for servers that require authentication is now encrypted in the file containing email settings for the ‘Direct’ email method.

·    When browsing for a path in various functions in PurchaseOrders releases dated after January 2016 on Windows 8 or higher, you had to select a file to select the folder. This was corrected by System Updater (2016.08.09), which is no longer required for this release of PurchaseOrders.

·    Filters were not rebuilt by DataCare for PurchaseOrders 9.2B causing empty results for all filters until they were explicitly refreshed in PurchaseOrders.

·    The snapshot made by the System Status function (chksys.exe) did not include station log files in some cases.

·    When taking a snapshot with the System Status function (chksys.exe), the error “Snapshot is incomplete! The snapshot encountered error (1).” was encountered in some cases, indicating a file was open and could not be included in the snapshot, when in fact that may not have been the case.

·    Installs a new Adagio Data Source (ADS) that prevents resource locking problems at large Adagio sites running 9.2 versions and improves application performance at these sites.

NOTE: All third-party applications from Adagio Developer Partners must use the new ADS. You must check with your Adagio consultant or the developer to confirm their application is using ADS 1.12. 66.3503 or higher. Failure to ascertain this risks corrupting data if the application is writing to the Adagio data files concurrently with Adagio modules.