Report Favorites allow saving Reports with specific options chosen. Click the Favorite button (a star icon) on any report dialog to create a Favorite. Favorites for a report can be accessed from the report dialog in a drop-down field. Favorites can be private to the Adagio user or public for use by all users. Private Favorites are yellow, Public Favorites are blue. Added Favorite Reports and Print/Delete Favorites functions to the Reports menu. Multiple favorites can be defined for the same report.
Report Sets allow the grouping of Report Favorites into a single print job that will run unattended. Report Sets may be printed to printer or PDF files (when Adagio ePrint is used). Report Sets may be launched from a command file or a scheduled Windows task by running Invoices.exe with the parameter /R followed by the Report Set (ex. /RDayEnd). A progress dialog lists the reports in the Report Set, the printing status of each, the destination folder, filename and conflict strategy. A log is generated that records the printing status of each report in the set. Use Report Sets to automate the printing of all your daily or month end reports.
Added 'Append by type' option to Payment Methods for the BankRec interface. Payment methods set to ‘Batch by date’ always created batches by date and by payment method. Now, if you have ‘Append to existing batch’, but do not have ‘Batch by date’, you can choose ‘Append by type’. This allows you to separate out the checks you deposit into two separate batches – checks drawn on the depositor’s (your) bank and checks drawn on other banks. It also allows you to separate checks and EFT payments of the same date for the same bank. To use this option you must have Adagio BankRec 8.1D or higher.
Added Payment Methods report.
Problems Fixed
In Receivables 9.0B (2011.07.27), cash transactions with a blank Payment Method were missing from the batch sent to the BankRec batch, unless an earlier entry with a Payment Method had been posted in the same batch or in a batch posted earlier in the same session.
In Receivables 9.0B, posting Debit Notes to Balance Forward customers caused data integrity errors.
An error occurred if you had more than 9,999 batches (for any batch type) in the same year. Note: the maximum number of batches allowed in a year is 65,535.
The Payment Method was not remembered between entries in Cash Batch entry.
If the 'Validate closed periods' option was set to 'Disallow', when there was an unposted batch from OrderEntry you could not post the batch and received an error indicating (incorrectly) that the fiscal period was closed for the date of the batch transactions.
In Receivables 9.0B (2011.07.27), after printing and clearing the Batch Status report for the entire range of batches, if there were no open batches, when you ran a Data Integrity Check (DIC) before creating a new batch it reported an error stating the next batch number should be 1. If you did a rebuild, everything appeared to fine. However, when you created new batches they became populated with the transactions from the original batch of the same number. This is now prevented. Note: if you only printed and cleared the Batch Status at Year End this was not a problem.
When the batch status information is cleared after printing the Batch Status report or by Period End, batch records for the associated batches are now also deleted. This may take a few minutes on a large database across a network. A progress bar is shown during this time. If the entire ranges is selected and there are no open batches this process will be instantaneous. When the batch status information is cleared at year end this process is also instantaneous. The Data Integrity Check now detects and removes orphan batch records for which there is no corresponding batch status record.
The Overdue Receivables report in Summary format formatted negative numbers differently in different columns.
If your Ledger data was created with version 9.0x and you had never used Ledger 8.1A or earlier versions, after printing the G/L Transactions report in Receivables, the Consolidate G/L Transactions dialog did not show the 2 options to consolidate by Fiscal Period.
The Company Name did not print on the Aged Trial Balance and other aging reports if there were no transactions in the range selected.
Several minor problems and inconsistencies with other modules related to ePrint functionality in Receivables have been corrected in this release. This includes some small new features. If you are using Adagio ePrint, Receivables 9.0C or higher is recommended.
The error message displayed when a user attempts to log in when the Security Group for the user does not exist indicated a different Security Group than the one actually missing for the user.
When installing Adagio to a computer or server where no Adagio modules had previously been installed, if you installed an Adagio module that does not use the Crystal print engine first (such as Lanpak or GridView), when you installed Receivables you received the error "Adagio has been established on destination folder: [x:\SOFTRAK]. Yet the install cannot detect the corresponding Reports Tables..." and were unable to proceed. If the first module installed uses the Crystal print engine there was no problem.
When running any Adagio module that installs vitalEsafe (or WebSafe as it was previously known as) on a Windows 7 (or Vista) station, in some cases the auto-workstation install ran every time you started the application, even if you had done a workstation install. This happened if the user was not an Administrator on their own machine (the default for a new computer) but rather a Standard user, and User Account Control (UAC) was on, and you had not installed any module with a release date of October 2011 or later and done a workstation install for it on the station. This has been resolved. To resolve this problem for ALL other modules, install any module with a release date of October 2011 or later and do a workstation install for it on the station.