Friday, July 8, 2011

Microsoft Forecaster 7.0 Service Packs Download Links

Microsoft Forecaster 7.0 SP4 has been released – See post by Jill


The Forecaster Team is always on top of things, and in the last few years I have noticed that any issue in Forecaster is usually resolved simply by installing the latest service pack. Most Forecaster updates are not very time consuming, and we try and make it a point to install the latest hotfix/service pack as soon as it is available.

The CustomerSource download links for Forecaster 7.0 and Service Packs 1 to 4 are below


Microsoft Forecaster 7.0 RTM Download
Version (7.0.1266.7) This is the RTM download for Forecaster 7.0.  

Microsoft Forecaster 7.0 SP1

CRITICAL: Make sure to apply the Critical Add-In for SP1 on the download page for SP1) (Version 7.0.1420.9 with SP1 when the Critical Add-in is install it will be 7.0.1420.10)- November 5, 2007 (Includes Hot Fixes 1-3)

Microsoft Forecaster 7.0 SP2

Version (7.0.1513.10) - June 24, 2008

Microsoft Forecaster 7.0 SP3

Version (7.0.1613.13) - April 22, 2009

--- Hot Fix (Only use with SP3)

Version (7.0.1618.20)   - December 15, 2010

Microsoft Forecaster 7.0 SP4

Version (7.0.1701.50 - June 27, 2011)


Microsoft Forecaster Issues Resolved by Forecaster Service Pack 4


No way to remove revenue account from revenue module once data has been associated.
Error displaying capital in detail report when using Allow drilldown to capital detail.


Deleting pay type association from salary grade creates orphaned records
Current users list doesn't work correctly on SQL Server 2005/2008.


The Multi-row tab doesn’t show the lines (rows), if an input set name is longer than 24 characters.
Start Period and End Period can’t be adjusted in HR Master after another field is changed.


Entering capital item into invalid period and deleting causes duplicate/orphan records
Excel Add-in returns no results when the optimization factor is 0.


Single Row Input with 'Suppress Zero Lines on Input' creates difference from Multi-row.
When using Human Resources Annually’ with regular allocations not selected, headcount is not updated for hourly employees.


Reports where lines are the departments show a zero balance
Copy plan wizard for HR Details does not correctly calculate allocation.

368241 System needs to keep deleted employees shaded while changing the “Show Allocation As” option.
Importing HR changes clears existing data in HR master but not in HR input.


Improve CALREV processing performance.
FTE not calculated correctly for employees distributed between multiple departments when specifying different employee options.


Running capital task on input set with historic periods causes results to shift the number of historic periods defined.
When reassigning an employee to a new department, the value in the Increase Period 2 field is not updated in the new department.


Allocation lost when reassigning an employee from two or more departments into one using the reassign window.
Error: “ExpressLink encountered a problem attempting to submit data to Microsoft Forecaster.” This occurs if the user name contains a period. (Ex. Jane.doe)


Decimal values do not appear on the single row tab
Temp tables do not get dropped on SQL Server 2000 when the username is numeric


When prompting for period and using a selection sub-menu in a report, users have to select period twice before the report will display.
If a user defined benefit exceeds 5,000 characters, Forecaster will close unexpectedly when trying to select it.


Enabling Auto-translate causes Forecaster to stop responding when adding employees in HR master.
If many options are created for a user defined benefit, Forecaster may close unexpectedly when trying to select an option in HR input.


The destination account and the contra account can’t be the same when two or more allocations are created and accumulate is used.
When sorting columns in the Multi-row tab, incorrect values can be created if a @LOOKUP calculation is also used.


Enabling Auto-translate causes Forecaster to stop responding when importing employees through HR import.
Forecaster closes unexpectedly.


If an employee from a previous input set salary grade doesn’t exist in a new input set, Forecaster closes expectedly when adding the employee.
Specifying a color for calculated columns doesn’t apply the color.


If Add as FTE is not selected when adding

No comments: