Effective Date: October 15, 2009
Updated: October 14, 2010
This file contains important information that was not available when the documentation for the product was written. Workarounds, when they are available, are provided for known issues.
The content in this Readme file applies to Microsoft Office PerformancePoint Server 2007 with Service Pack 3 (SP3). PerformancePoint Server 2007 contains two major parts, each of which can be deployed separately:
PerformancePoint Monitoring and Analytics
Information in this Readme file pertains to both parts of the product.
Note: For the most current and detailed information about this service pack release, refer to documentation in the following locations:
Copyright © 2010 Microsoft Corporation. All rights reserved.
What's new in PerformancePoint Server 2007 SP3?
PerformancePoint Server 2007 SP3 includes the following new features, changes, and improvements:
Monitoring and Analytics
New features, enhancements or fixes:
- Support for the Windows 7 operating system.
- Improved messaging when a filter or other selection returns no rows or columns in an analytic grid.
- You can now install PerformancePoint Monitoring Server and PerformancePoint Dashboard Designer on a machine that has .NET 3.5 already installed.
- Improved handling of scrolling on very large dashboard pages from within Dashboard Designer.
- Improved handling of zone adjustments in Dashboard Designer.
- Improved usability of the PerformancePoint Server Web Parts
- Improved Time Intelligence calendar control. This enables easier filtering on dates.
- Better handling for connecting to SQL Server Reporting Services (SSRS) 2008 reports and for displaying SSRS multi-select filter reports.
- Better handling when display conditions and stacked zones are both in use.
- Excel Services report views now load into Dashboard Designer, even with no SharePoint root site.
- Improved analytic chart, show details, and scorecard formatting when exporting to Microsoft Office Excel.
- Improved drill-through functionality on analytic reports.
- Font-size changes in scorecards are appropriately displayed in published dashboards.
- Better handling of scorecard KPIs when using named sets.
- Improved integration with Excel Services: Excel Services reports display properly in dashboards. Empty cells no longer prevent the dashboard author from connecting to the data source in Dashboard Designer.
- Better migration support: analytic charts and grids that are created with SQL Server 2005 Analysis Services data can be updated to use SQL Server 2008 Analysis Services data.
- Improved integration with SharePoint: Now you can use the edit mode in Microsoft Office SharePoint Server or Windows SharePoint Services to add a SharePoint Web Part to a PerformancePoint dashboard; SharePoint style sheets no longer override cell-level font size and font-family settings.
- Improved integration with ProClarity: PerformancePoint Server filters passed to ProClarity reports retain the correct hierarchical order. Sorting of columns in a ProClarity report that is displayed in a PerformancePoint Web Part is now more effective.
- Customers can now upload their own custom Help into PerformancePoint Web Parts.
- Support for the Windows 7 operating system.
- Submitting line-item details with assignments. This new feature enables users to add, edit, view, and submit line item details. They can also view the submitted line-item details in reports.
- Adjusting security with the PPSCmd utility. This feature enables users to lower security changes within PPSCMD. For example, it is now possible to move security from Read/Write to Read Only within the PPSCMD utility.
- Extending the calendar beyond 25 years. This feature enables users to manually change the maximum limit of future years to a value greater than 25 and less than or equal to 200.
PerformancePoint Monitoring and Analytics Known Issues
The following are known issues for Monitoring and Analytics.
|Changing zone settings from horizontal to vertical in Dashboard Designer causes an unhandled exception error.
||Limit the number of zones in a dashboard to three columns.
|When the data includes ISBN numbers, the initial zero is dropped from the ISBN IDs.
||Replace the initial zero with a non-numeric character.
|When you view a dashboard through Internet Explorer 8 (IE8) the menu for an analytic chart might show up behind the main menu or on the right side for the first window and behind the main menu for the second window.
Fix this by changing your IE settings for both the Internet and your Local intranet.
- From the IE Tools menu, select Internet Options.
- Select the Security tab.
- Click Custom level. The Security Settings – Internet Zone dialog box will open.
- In the Miscellaneous section of the dialog box, look for the Allow script-initiated windows without size or position constraints option and select Enable.
- Click OK to close the dialog box.
|When a strategy map is configured to “Render as Image,” dashboard users might not be able to view or use the strategy map.
“Render as Image” causes a strategy map to display as a static image. We do not recommend using this setting.
However, you can fix this by downloading Microsoft Visio 2007 Viewer on all dashboard consumers’ computers. To download and install Visio 2007 Viewer, visit the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=180023).
PerformancePoint Planning Known Issues
The following are known issues for Planning.
|You cannot use 64-bit versions of Microsoft Office Excel with PerformancePoint Planning applications.
||Planning Business Modeler and PerformancePoint Add-in for Excel are 32-bit applications. They do not support a 64-bit version of Microsoft Office Excel.
|An Unhandled Exception error occurs when you open a Reporting Services report.
||Download the Report Viewer Redistributable 2008 (http://go.microsoft.com/fwlink/?LinkId=166912).
|The PPS SP3 Planning module, when patched with the June CU, will extend support to Office 2010, IE8, SQL Server 2008 R2, Windows 7, and Windows Server 2008 R2. Please note, however, that our product group does not plan to extend support beyond these platforms.
Language-Specific Known Issues
The following are known language-specific issues.
|When you deploy the Alpine Ski House (ASH) application under a Japanese operating system, deployment of the ResortMgmt subsite fails.
||To deploy the ASH application successfully on a Japanese operating system, you must use the following short-date format: yyyy/mm/dd.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
Copyright 2010 Microsoft Corporation. All rights reserved.
Microsoft, Excel, PerformancePoint, ProClarity, and SharePoint are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.
Top of Page