PlanGuru Customers, here is a list of fixes and improvements that have been released as part of the 188.8.131.52 Update for PlanGuru 2012.
Manual Updates to the balance sheet - Customers were noting that they had to update balance sheet cells twice when entering values directly into the grid using the 'Entered by User' method. This has been fixed, balance sheet balances can now be updated upon the first update attempt as they were on the income statement.
Analysis Name Change Issue - Customers who were using PlanGuru in the cloud (or in certain network environments) were reporting issues when changing the name of analysis files. When this feature was used the name of the .accdb file got updated while the name of .xml file didn't. This was causing the analysis files to be inconsistently named and resulted in confusion and the need to manually rename the .accdb file in Windows Explorer for the analysis to opened correctly. This has been fix, this feature can now be used in all installation approaches.
Import Utility Negative Signs on Credit Balances - When importing debits and credits from separate columns using the Excel import utility, negative signs ("-") in front of credit balances results in a confusing error message. The error message now clearly indicates that if debits and credits are imported separately values must be expressed as a positive.
Notes Payable Wizard Bug - In rare circumstances deleting the last sequentially ordered note (setup using the Notes Payable Wizard) was causing the other notes to be converted to the 'Entered by User' method. This has been fixed.
Notes Payable Wizard Current Portion of Long Term Debt - When users setup a note using the 'Existing' note option, the ability to link to a current portion of long term debt was only available the first time the NP wizard setup menu. On successive updates the current portion link dialog was no longer available and the link between long term and current portion of the note was disrupted. This has been fixed.
"admin" Login Issue - One user reported an issue where they logged in using the 'admin' login (should be a 'Admin', note the capital "A"). PlanGuru accepted the user ID and password, but didn't give the user full administrative rights. This was corrected by only allowing users to login with the 'Admin' user ID.
Improved Windows Insufficient Privileges Error Message - In the past when users ran into issues related to insufficient Windows permissions they received a cryptic and uninformative error message. Error messaging in this area has been improved to clearly communicate that the issue relates to insufficient Windows privileges. Users will now be informed that they should contact their internal IT staff to update their permissions accordingly.
Cash Flow Description Length - Some users of the Advanced Reporting Add-In ran into issues when cash flow descriptions exceeded the maximum allowable field length. This issue has been corrected so that cash flow descriptions are appropriately truncated to meet the allowable field length.
Consolidation Issue - In rare circumstances (more specifically when a user added an additional operating expense class that shared the same name as the default operating expense class "Operating Expenses") categories were getting duplicated during the creation of the consolidation. The total balances were still correct, however the duplicate categories were being created and consequently cluttering up the consolidation analysis. This issue has been fixed.
Link to Excel - Users were reporting issues when linking to an Excel file that was also an active report built using the ARA. When a customer was trying to link to cells in the first tab they had to put the focus on to another worksheet before they were able to link the desired cells. This has been fixed.
WH Taxes and Accrued Expenses - When using the "WH Taxes and Accrued Expenses" forecasting method, if the current liability is deleted the category it was linked to is no longer available for selection when a new current liability is added using this same forecast method. This issue has been fixed.