Adagio Ledger 9.3A

·    Close is now the default on the confirmation message: “Batch entry is out of balance”. This allows Adagio XConsole to close a batch if a user is editing a batch that is not in balance. The batch will be saved in the out of balance condition.

·    In Ledger 9.2A and 9.3A, the ‘Restrict to Subledgers’ option in an account was not working properly for JobCost.

·    Source Journals did not print all the entries when the periods span 2 years and the second year has an A.

·    When ExcelDirect printing the Detail Listing report, the date format used in Excel is now from the User Preferences, Report Options tab 'Date format (Detail)' field.

·    Printing Statement Groups to PDF through report sets was displaying an AdagioV2PDF message even though 'Lock PDF setup?' was enabled in the Company Profile. It no longer displays the message.

·    Printing the Trial Balance report using a Favorite with the 'Current year/period only' option did not make the Fiscal Period uneditable.

·    Printing the Detail Listing report using a Favorite with the 'Current year/period only' or 'Curr. year/prev period only' option did not set the starting and ending Fiscal Periods properly. When printing from a Report favorite, the Fiscal Periods defaulted to 1 to 12 instead of the Current period or Previous period. Printing from a Report set or the Print/Delete Favorites function worked properly.

·    The “Opening Balance” label did not print on the Detail Listing report for some accounts when printed with certain report options selected.

·    When report options were restored in User Preferences for All Users, the ExcelDirect filename in any report favorite for the Detail Listing was changed when it should not have been.

·    Corrected error that occurred in rare cases at some sites when retrieving batches containing transactions with links to DocStore documents from subledgers.

·    Import Header Detail batches was requiring the Det-Source Code to be in the import file or a message would appear: 'Default currency code is invalid.'.

·    Importing with Field offset was trimming the import field on the right instead of the left.

·    Export transactions failed for record counts exceeding 256,000.

·    Using an automation command to import transactions indicated success but did not actually write the new records to the transactions file. This has been fixed.

·    Automation has been updated to support importing batches from other systems that may have Unbalanced entries. For Automation imports, the Unbalanced Batch Warning message will default to 'Yes to All'.

·    Merging DocStore files inside the Maintain Documents window will now correctly merge the selected files into 1 document.

·    There was an error when creating a new database in Ledger 9.3A (2018.04.22).

·    The Data Integrity Check now corrects (removes) orphaned provisional posted batches from the current batch.

·    If you posted in Ledger while DataCare was open, then checked the database in DataCare without first closing it, DataCare falsely reported an error in Ledger.

·    When opening a database, if the data path folder name contained a period, browsing to the folder and double clicking on the global file caused the application to try to create a new dataset with the extension set to the part of the folder name following the period character.

·    The process which emails the Automation Log was modified to use the Display name of the Email setup instead of the Account name. The subject line was also changed to indicate whether reports are attached or not.

The Automation command EmailPDFAutoLog within modules did not work when you used the Office 365 SMTP server as your Mail Server for Direct.