Hello PlanGuru users. We are pleased to announce that our first maintenance update for PlanGuru 2014 has just been released. Some of the fixes included are listed below:
“Group Cash Flow Detail by Subclass” Unhandled Exception Error – Some users experienced an error when they tried to use the “Group Cash Flow Detail by Subclass” feature. This error would prevent the user from viewing the cash flow, and would generate an unhandled exception. This issue has been corrected in this maintenance update.
Treatment of Adjust prior period categories when rolling forward – There was an issue regarding the treatment of “Adjust prior period” (now growth rate) categories when an analysis was rolled forward. This issue would cause categories using this projection method to not get rolled forward in the same way other projection methods would handle it. This led to data getting populated in to the wrong year.
Treatment of actuals during Rollforward – When some users performed a rollforward they noticed that if they had pushed actual data in to their budgeted periods, those periods would be blank when the rollforward finished. This problem has been corrected in this update.
Excel Linked rows initially display 0s when actuals are used in Rollforward Utility – A problem linked to the one above, when an analysis was rolled forward categories using the “Link to Excel” projection method would display as a 0 at first.
Tutorial video link cleanup – Some of the “Watch a tutorial” buttons took users to the wrong video, or the button did not function at all. This issue has been fixed so that all links will take you to the correct video now.
Issue Importing Notes Payable – Users were having difficulty importing note payables. When they tried mapping notes in to the “Long Term Liabilities” section the category name would get pulled in, but no data would be imported. This would cause balance sheets to become unbalanced and several other issues. This has been fixed as of this maintenance update.
Excel Import: Mapping more than two categories to “Taxes based on net income” – In Planguru you are unable to create more than two categories that use the “Taxes based on net income” subclass. You could still map more than two categories to that subclass though, which would result in an unhandled exception when trying to complete the Excel import. As of this update the import process now warns the user that they mapped more than two accounts to that subclass.
Prior Period selector causing issue with formulas created in 2013 version - A new feature to Planguru 2014 is the ability to specify a prior period using a selector. This causes an issue for formulas referencing a prior period created in the 2013 version. Users would get an unhandled exception when trying to open a formula category because the program would now know which specific prior period to reference. This issue is fixed in this update.
Beginning and Ending inventory subclass unhandled exception – When a user marked a category using the “Beginning Inventory” or “Ending Inventory” subclass the user could exit the menu without selecting what category it should reference. This would cause an incomplete formula and cause several totals not to calculate at all, or not calculate correctly. Now the user has to specify which category to link to before they can exit the menu.
Quickbooks Import Unhandled Exception – When a user is selecting periods to import in to using the Quickbooks import utility, if a user used the down arrow, and space bar to select dates it was possible for them to get in to a blank box that was not attached to any date. If they pressed space, or added any other character, upon trying to continue with the import the user would get an unhandled exception. This update now prevents the user from getting in to that box.
Gain (loss) on disposition of fixed asset error – When a user created a category in the “Other Income (Expense)” class, and used the “Gain (loss) on disposition of fixed asset” the spread to enter data would not actually appear. This issue has been addressed and corrected
Issue with VAT computation – Some users reported an error having to do with VAT computations. If they had an analysis set up so that their second and/or third year was budgeted as a full year instead of broken down by periods, and they had some categories that were not subject to VAT, that VAT value would calculate incorrectly. This has been fixed in the update.