PerformancePoint Monitoring and Analytics Readme


Effective Date: December 8, 2008

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 the PerformancePoint Monitoring components of Microsoft Office PerformancePoint Server 2007 with Service Pack 2 (SP2). These include:

·         PerformancePoint Monitoring Server

·         PerformancePoint Dashboard Designer

·         PerformancePoint Dashboard Viewer for SharePoint Services.

Copyright © 2008 Microsoft Corporation. All rights reserved.


What's New in PerformancePoint Server 2007 SP2?

Using PerformancePoint Server 2007 SP2 with SQL Server 2008

PerformancePoint Monitoring Server Known Issues

PerformancePoint Dashboard Designer Known Issues

PerformancePoint Dashboard Viewer for SharePoint Services Known Issues

Legal Notice

What's new in PerformancePoint Server 2007 SP2?

PerformancePoint Server 2007 SP2 includes the following changes and additions to PerformancePoint Monitoring components:



You can now use SQL Server 2008 with PerformancePoint Server 2007 SP2.

Important: To use SQL Server 2008 with PerformancePoint Server, you must first download and install the Cumulative update package 9 for SQL Server 2005 Service Pack 2 ( In addition, you must install the Feature Pack for SQL Server 2005 ( Install the cumulative update and the feature pack on the server where PerformancePoint Server 2007 SP2 will be installed.

You can now use the Show Details action on PerfomancePoint reports that use data that is stored in SQL Server 2008 Analysis Services.

Show Details enables dashboard consumers to right-click in a cell or on a chart value and see the transaction-level details for that value.

PerformancePoint Server 2007 with SP2 now supports Windows Server 2008 Hyper-V.

Hyper-V creates new opportunities for server virtualization. You can use Hyper-V to make more efficient use of system hardware and host operating system resources to reduce the overhead associated with virtualization.

For more information, see the PerformancePoint Server 2007 Hyper-V guide (

You can now use Dashboard Designer on a computer that is running .NET Framework 3.5 alongside .NET Framework 2.0.

You must install .NET Framework 2.0 before you install .NET Framework 3.5.

You can now use PerformancePoint Server with domains that have apostrophes in their names

In previous versions of PerformancePoint Server, when a domain name included an apostrophe, the configuration tool failed for both Planning Server and Monitoring Server.

Scorecard key performance indicator (KPI) queries are improved.  

Timeout errors no longer occur with scorecard key performance indicators (KPIs) that use data that is stored in SQL Server 2005 Analysis Services.

Time Intelligence Post Formula filters now display the correct number of days for each month.

In previous versions of PerformancePoint Server, the calendar control for Time Intelligence Post Formula filters sometimes displayed 31 days for each month. This is no longer the case.

Time Intelligence filters now work on scorecard KPIs that use data that is stored in Analysis Services

In previous versions of PerformancePoint Server, some Time Intelligence expressions caused filters that were linked to KPIs to fail.

For example, when a compound expression such as (Day-7:Day-1) was used in a Time Intelligence Post Formula filter and that filter was linked to a KPI, an error message occurred. In PerformancePoint Server 2007 PS2, single and compound Time Intelligence expressions work with KPIs that use data that is stored in Analysis Services.


Using PerformancePoint Server 2007 SP2 with SQL Server 2008

To use SQL Server 2008 with PerformancePoint Server 2007 SP2, you must have the following installed:

·         Feature Pack for SQL Server 2005 (

·         SQL Server Cumulative Update 9 redistributable files (

·         SQLNCLI

·         SQL Server 2005 ADOMD

·         SQL Server 2005 ASOLEDB9

·         SQL Server 2005 XMO

For more information, see the following:

·         Install PerformancePoint Monitoring Server with SQL Server 2008 (

·         Upgrade SQL Server 2005 to SQL Server 2008 with PerformancePoint Monitoring Server (


PerformancePoint Monitoring Server Known Issues

The following are known issues for Monitoring Server.



When you are using PerformancePoint Server 2007 SP2 with Windows Server 2008 or Windows Server 2008 Hyper-V, you cannot deploy a dashboard to a preview.

You can only preview a dashboard when you enable anonymous authentication and use the application pool identity.


Workaround:   Follow these steps:

1.      Open Internet Information Services (IIS) Manager by clicking Start > All Program > Administrative Tools > Internet Information Services Manager.

2.      In the Connections pane, expand Sites, and then expand PPS Monitoring. Double-click Preview.

3.      In the center pane, under IIS, double-click Authentication.

4.      Right-click Anonymous Authentication, and then click Enable.

5.      Right-click Anonymous Authentication again, and then click Edit.

6.      In the Edit Anonymous Authentication Credentials dialog box, select Application Pool Identity. Click OK.

7.      Reset IIS for your changes to take effect.

PerformancePoint dashboard filters are displayed with wrapped text in dashboards that contain two or more horizontal zones.

This can occur because the white-space: nowrap clause is absent in one or more of the cascading style sheets (CSS) that are used by Monitoring Server.


Workaround:   Take the following steps:

1.      On the computer that has Monitoring Server installed, log on as an administrator.

2.      Open the command prompt.

3.      At the command prompt, type the following:

copy /Y

"%ProgramFiles%\Microsoft Office PerformancePoint Server\3.0\

 "%ProgramFiles%\Common Files\Microsoft Shared\
web server extensions\wpresources\

4.      Exit the command prompt.

An "access denied" error occurs if you run Monitoring Server Configuration Manager at the same time that you are trying to install Dashboard Viewer for SharePoint services.

Monitoring Server Configuration Manager requires that the user specify the SharePoint site collection when Dashboard Viewer for SharePoint Services is selected for installation.


The "access denied" error occurs because the installing user is not a SharePoint site collection administrator on the selected site.

Note   By default, SharePoint farm administrators and Server administrators do not have permission to open or read sites. If necessary, they can take ownership of a site collection by adding themselves as site collection administrators.

Verify that the installing user is a site collection administrator on the selected site, and then rerun Monitoring Server Configuration Manager.

1.      Open SharePoint Central Administration.

2.      Click the Application Management tab.

3.      Under SharePoint Site Management, click Site collection administrators.


Workaround:   None. By Design.

Scorecards that have KPIs that are based on SQL Server tabular data may show "ERROR" when you view them in SharePoint Services, even if they appear to be working correctly in Dashboard Designer.

When you create a KPI from a SQL Server tabular data source, the published dashboard on SharePoint Services displays the word “ERROR” where the KPI data should be. The error text appears because the underlying permissions on the data source prevent access to the data. This occurs when there are mismatched permissions between the SharePoint server and Monitoring Server.

The identity of the SharePoint application pool is used to connect to data sources when a dashboard is deployed to SharePoint, and the identity of the PerformancePoint application pools is used when in the designer. Both application pools must use the same identity for security to work consistently.


Workaround:   This is by design. Make sure that the application pool identities for the SharePoint server and Monitoring Server are identical in Internet Information Services (IIS) Manager.

If you hide an Analysis Services 2005 cube that has perspectives, filters, analytic reports, and scorecards may not display data.

When you are using filters, analytic reports, and scorecards that are based on Analysis Services 2005 cubes that have perspectives, and the "Visible" property is set to "False," your data source connection may not work, and error messages may occur.

In Dashboard Designer, this issue may arise when you are using the Member Selector dialog box for analytic reports and scorecards, or when you are navigating the Details pane for these elements. In Dashboard Viewer for SharePoint Services, this issue may arise when users attempt to use filters or navigate within analytic reports or scorecards.


Workaround:   Make sure the "Visible" property is set to "True" in the Analysis Services cube.

If you delete one or more files (but not all) in the ClickOnce cache directory, Dashboard Designer may not launch correctly the next time that you click its name in the Start menu.

The ClickOnce cache directory (C:\Documents and Settings\username\Local Settings\Apps\2.0) must either contain all its files, or it must be completely cleared in order for Dashboard Designer to launch.


Workaround:   Remove all of the files in the ClickOnce cache directory.

Two versions of the Sample guides are in the Monitoring Samples folder: one in the .msi file, and the other in the Monitoring Samples folder.

You will find the Monitoring Sample Guide and the Monitoring Scorecards Sample document in both the .msi file and the Samples folder. These documents are designed to help you view and use the sample files (which include dashboards and scorecards).

The original documents are included in the .msi file, but in our efforts to provide you with the most up-to-date content, we have placed later versions of these documents in the Samples folder. We recommend that you use the updated versions of the documents.

To open the most current documents, browse to C:\Program Files\Microsoft Office PerformancePoint Server\3.0\Samples, and then open the files that are named "PPS Monitoring Sample Scorecards.doc" and "PPS Monitoring Sample Guide.doc."


Workaround:   None.

When you attempt to restore the sample data PDW.abf file by using SQL Server 2005 Analysis Services, you get an error message.

The error message reads, "The level '[1-08]' object was not found in the cube when the string, [Time].[Week].[1-08], was parsed. (Microsoft.AnalysisServices."

This occurs because the PDW data cube contains a Current Week calculated member that resolves to a time period in 2008, and the data cube does not contain 2008 data.


Workaround:   Do one of the following:

·         Locate the calculated member in the data cube, remove it, and then process the cube, or

·         See the article titled, "Error Restoring PDW sample data cube in 2008" posted at the PerformancePoint Team Blog on MSDN (

You cannot deploy Monitoring Server on Windows XP or Windows Vista operating systems.

Although you can use computers that are running Windows XP or Windows Vista to develop or preview applications for Monitoring Server, you must deploy Monitoring Server on a computer that is running Windows Server 2003 or Windows Server 2008.


Workaround:   None.

You cannot use Monitoring Server with SQL Server 2000.

Workaround:   None.

Extranet deployments are not supported by PerformancePoint Server 2007.


To view and access PerformancePoint data, users must be authenticated on computers that are joined to a trusted Active Directory service domain.


Workaround:   None.

PerformancePoint Server 2007 does not support single-server multi-tenant environments.

To set up a multi-tenant environment for data or users, you must use multiple servers.


Workaround:   None.

External Connector (EC) licenses do not imply or declare capabilities such as extranet or hosting support.

The EC is an alternative licensing model that permits any number of users with a valid Active Directory domain account on a computer that is joined to access PerformancePoint Server 2007.


Workaround:   None.


PerformancePoint Dashboard Designer Known Issues

The following are known issues for Dashboard Designer.



When you use Dashboard Designer to include a Reporting Services report in a dashboard, you may get an "unhandled exception" error message.

The error message occurs because the ReportViewer component in Reporting Services is missing.


Workaround:   Download and install the Microsoft Report Viewer Resdistributable 2005 from the Microsoft Download Center (

When you use Dashboard Designer to include a SQL Server 2005 Reporting Services report in a dashboard, the date that appears in the First Create Datetime box may render incorrectly.

This can occur when the Reporting Services report uses a date format that is specific to a particular locale. For example, the date may appear in the format mm/dd/yyyy when it should appear as dd/mm/yyyy.


Workaround:   Download and install the Cumulative update package 4 for SQL Server 2005 Service Pack 2 (

When you deploy a scorecard to SQL Server 2008 Reporting Services, users may get an error message when they attempt to view the scorecard.

This can occur when you deploy a scorecard that uses data that is stored in Analysis Services. It is caused by security settings in SQL Server 2008.


Workaround:   When you deploy a scorecard to Reporting Services, specify the following settings:

·         Select the Use credentials stored securely in the report server option

·         Type the user name (in the format DOMAIN\username) and password.

·         Select the Use as Windows credentials when connecting to the data source option.

When you select the option to hide the target indicator, the image on a scorecard yields a red "X."

An artwork placeholder (a box that has a red X) displays next to the target value when you deploy a scorecard to a SQL Server Reporting Services server. This occurs when the "Show Indicator Image" check box is cleared on the Target Settings dialog box.


Workaround:   None.

A period (".") or square bracket (“[" or "]”) in an Excel column heading is replaced with different characters.


When a user creates an Excel data source that has a column name that contains a period ("."), then clicks Accept Changes, a number sign ("#") displays in place of the period. 

Example:   The column heading Customer.Country becomes Customer#Country.

If a left square bracket is used, it is replaced with an opening parenthesis; a right square bracket is replaced with a closing parenthesis.

Example:   The column heading Customer[Country] becomes Customer(Country).


Workaround:   From the Workspace Browser, double-click the Excel data source that you want to change. Click the View tab and then highlight the column that you want to change. On the Details pane manually update the Column Name.

Changes made to permissions on an Analysis Services data source are not immediately reflected on Analytic Chart or Analytic Grid reports

Changes made to the permissions on an Analysis Services data source within Dashboard Designer are not effective until the data refresh rate that is designated in the cache settings has completed a cycle. The default setting is 10 minutes. This affects Analytic Charts and Grids only.


Workaround:   After making changes to permissions, right-click the analytic report that draws its data from the edited Analysis Services data source. Click Publish. The report will be updated with the current permission levels.

Tabular filters can only use columns with data stored as a string for the "Key" or "Parent Key" fields

When you create a tabular filter, if a non-string column is selected for the Key or Parent Key, the filter will not work. When the filter contains a non-string key column, you will not be able to join the filter with its data table fails because all data source member-type are string columns.


Workaround:   Select only those columns whose data is stored as a string for the "Key" or "Parent Key" values.

Trend predictions may vary if a scorecard contains both actuals and targets.

Currently, when both Actual and Target columns are in a scorecard, the forecasting algorithm cannot ignore one column or the other. The result is trend predictions that are based on a combination of all actuals and targets in the scorecard.


Workaround:   To forecast actuals, build a scorecard that contains only Actual columns. To forecast targets, build a scorecard that contains only Target columns. 

You cannot use Display Condition functionality on scorecards when you are using the Japanese version of Dashboard Designer.

Workaround:   None.

Existing indicators that have been modified may not render correctly in a dashboard element.


When you create a scorecard, you may not be able to publish its dependent indicators by clicking Publish All for the scorecard. Before you publish the scorecard, publish indicators individually. Do this by right-clicking each one and then clicking Publish All in the shortcut menu.


Workaround:   Publish individual indicators first, and then publish the scorecard.

When you use a custom MDX query to apply multiple selections to the background of an analytic report, Drill to Detail may return too much data (as if no filter were applied), and the Show Information and Show Details features may not display the appropriate messages.

The selection is aggregated by Analysis Services; however, ADOMD reports the filter axis (items on background) as null, which is interpreted to mean there are no selections on the background. The value, returned as null, is why the Show Information feature displays the message "No background selections show" and why the Show Details option does not display the "Can't drill to details because of multiple selections on background" message like it should.

Drill to Detail uses the default member on that hierarchy because the actual selections are not reported in the results. Therefore, more data is returned than expected.


Workaround:   None.

In a scorecard with a time intelligence filter, time periods are always arranged in chronological order.

When a scorecard is set up with a time intelligence filter, time periods are arranged in chronological order. This occurs even when the filter specifies a different order, such as Month:Month-6, because of an issue within MDX.


Workaround:   None.

Even though you click Publish All, the Analysis Services data sources that are saved in your workspace are not published.

Analysis Services data sources that appear in your workspace may not be published correctly when you click Publish All (on the Home tab).


Workaround:   First click Mark Differences, and then click Publish All.

When you export a report or a scorecard from a SQL Server Reporting Services report to Office Excel, the scorecard or report may not render correctly.

The rows and columns in the scorecard can be transposed when you export the scorecard to Excel.


Workaround:   If the document map that is associated with the Reporting Services report is available, you can use it to locate the data that you need. Select an item in the document map and it will take you directly to the appropriate cell in the Excel file.

If you rename and redeploy a scorecard (that has GB18030 characters in the file name) to one folder in Reporting Services, only one scorecard will appear in the folder.

This is a Reporting Services issue.


Workaround:   You can rename the scorecard by using entirely different characters or deploy the scorecard to a different folder in Reporting Services.

If you resize the Dashboard Designer application window when you are working on analytic reports, the program terminates.

When you are using Dashboard Designer on a computer that is running Windows Server 2003 x64 bit edition, and attempt to resize the application window, the application may either terminate or display an error message. This can occur when you are creating or editing analytic charts or grids.


Workaround:   You can do one of the following:

·         Click Continue on the error message and keep working (the application will not be resized)

·         Double-click a different type of dashboard element (such as a data source, KPI, indicator, or scorecard) in the Workspace Browser, resize the application, and then create or edit the analytic report.

Duplicate permissions can cause error messages in Dashboard Designer.

Listing users more than once with the same role for an element can cause error messages. For example, a user who is assigned more than once to a data source, report, scorecard, dashboard page, indicator, or KPI can cause an error message to appear. The message states that duplicate permissions were found. When this occurs, Dashboard Designer uses the first instance of the user in the list.


Workaround:   Avoid assigning duplicate permissions to elements in Dashboard Designer. You can also delete duplicate permissions by using the Properties tab in the workspace.

If you add a custom property of the Date type, you may see an error message that says, "Not a valid date."

This error message may appear, even if the date is valid.


Workaround:   In the Value column, enter a date. Use the date format that matches the regional settings for the computer that you are using for Dashboard Designer.

When you are creating a report that uses SQL Server tabular data on a computer that does not have SQL Server 2005 SP2 installed, you can get an error message.

The "unhandled exception" error message appears because the ReportViewer component in SQL Server Reporting Services is missing.


Workaround:   Download and install the Microsoft Report Viewer Redistributable 2008 component from the Microsoft Downloads site:

You cannot use a tabular values filter as a member selection filter.

When you create a tabular values filter and link it to a report or a scorecard that uses a tabular data source, the filter does not work.


Workaround:   Create a dashboard filter by using the Member Selection filter template instead.

You cannot use Shape Data Graphics to connect a KPI to a shape in a strategy map.

The Visio Viewer ActiveX control does not support using Shape Data Graphics to display values.


Workaround:   Insert data into the text of a shape by using the following procedure:

1.      Double-click a shape, and then right-click in the shape. Click Insert Field.

2.      Select Shape Data, and then select the appropriate field that you want to use.


Dashboard Viewer for SharePoint Services Known Issues

The following are known issues for Dashboard Viewer for SharePoint Services.



Analytic charts and grids that are exported to Excel do not display the Display Name property

When you export an analytic chart or grid to Excel through SharePoint Services, the Display Name for dimension members does not appear. Instead, you see the Member Unique Name property.


Workaround:   None. 

Trend analysis, PivotChart, and PivotTable charts may not display correctly on a SharePoint Web site

When a trend analysis, PivotChart, or PivotTable chart is added to a dashboard, and then the dashboard is exported to SharePoint Services that is running on a 64-bit operating system, the chart is not displayed on the resulting SharePoint Web page. This occurs because Office Web Components (OWC), which renders the image, is not compatible with 64-bit environments.


Workaround:   None.

The Show Details feature causes an extra browser window to open in Windows Vista.

When you are using a dashboard that has been deployed to a SharePoint site and your computer is running Windows Vista, applying the Show Details command to an analytic chart or grid in the dashboard can cause an extra browser window to open. This may be due to the Windows Vista user account control (UAC) security feature.


Workaround:   Make sure that the UAC is turned off.

Filter Lists display behind reports.

If a filter list was created on a deployed dashboard by using the List or Multi-Select display method, it will display behind the report. This affects PivotTable, PivotChart, Excel Worksheet, Strategy Map, and Trend Chart report types.


Workaround:   Use either of the following workarounds:

·         Design the layout of your dashboard so that these report types display under or to the side of the filter controls.

·         After putting the report on the dashboard layout, click the arrow on the Web Part and then select Edit Item. Select the Render as Image check box and then click OK. This renders the report as an image for the current dashboard page only.

You receive a DDE Error when you try to export Drill to Detail action results to Excel 2007

An error may display and the file does not open correctly after you export a detail report from an analytic grid or chart view to Excel 2007.


Workaround:   If you receive an error after exporting a detail report from an analytic grid or chart view to Excel, click Save to save the Excel worksheet to your computer. After that, you can open the detail view file successfully in Excel.

ProClarity Analytics Server Page Report "Resize Image" functionality does not work in a dashboard

When a ProClarity Analytics Server Page report is created by using an analytic chart and is deployed to SharePoint Services, and then the browser window size is changed, the ProClarity Analytics Server Page report displays a Resize Image button, but it either does not work or it works inconsistently.


Workaround:   None.

When you redeploy a dashboard (or deploy a new dashboard that has the same name), SharePoint is case insensitive to file names.

When there is a capitalization error in the name of a dashboard that is deployed to a SharePoint site, you cannot correct the capitalization issue by redeploying the dashboard with the same name. SharePoint is not case sensitive.


Workaround:   Update the folder name in the SharePoint site that contains the dashboard, and then redeploy the dashboard (with the correct capitalization) to the updated folder. 


Strategy maps in a deployed dashboard may not export to Office Excel or Office PowerPoint correctly. Strategy maps that are configured to render as images may not display correctly in the dashboard.

By default, the strategy map report type does not support the following functionalities:

·         Export to PowerPoint

·         Export to Export

·         Render as Image


Workaround:   This is by design. To enable the exporting functionality, make sure that Office Visio is installed on the Windows SharePoint Services server and that the web.config file for SharePoint is modified. See the PerformancePoint Server 2007 Deployment Guide (

The Show Details action in a scorecard that is based on Analysis Services can produce an error message that states that you do not have permissions.

In some cases, the Show Details action that is performed on a scorecard cell can produce an error message that states, "You don't have permissions to show details for the cell." This can occur even when you do have permissions to view the scorecard in Monitoring Server.

Analysis Services requires separate permissions to use Show Details functionality. The scorecard can render correctly in a dashboard even when these separate permissions in Analysis Services are not yet assigned.


Workaround:   Contact an IT Administrator to make sure that permissions are correctly assigned in Analysis Services. For more information, see Granting User Access (

The Show Details action in a scorecard that is based on Analysis Services data is not available.

Scorecards that are based on Analysis Services data may not have the Show Details option, even when Show Details is enabled in the cube. This can occur when the KPI Calculation settings are not set to Source Data.


Workaround:   Contact an IT Administrator to make sure that KPI Calculation settings are set to Source Data (and not Default) for each KPI in the scorecard.

When you drill down to a different dimension in an analytic chart that uses a filter, an error message appears.

When a filter is applied to an analytic chart and the hierarchy level in the filter is different from the hierarchy level that applies to the chart, drilling down to a different dimension in the chart can cause an error message to appear.


Workaround:   Do one of the following:

·         Make sure that the hierarchy level that is used in the filter matches the hierarchy level that is used in the chart.

·         Change the view to an analytic grid and then drill down to a different dimension. You can do this by opening the analytic chart in a new window and then selecting the Grid toolbar command.

You receive a "404 Error" or "Page Not Found" error message when you attempt to view ProClarity Analytics Server Page reports in a dashboard that has been deployed to a SharePoint site.

The ProClarity Analytics Server Page report type requires the application of a hotfix to the server (Microsoft ProClarity Analytics Server 6.3) that is used to render the reports. This hotfix allows PerformancePoint Server to interact with ProClarity Analytics Server.

ProClarity Analytics Server 6.3.2209 must be installed before you can download and use the hotfix.


Workaround:   Download the hotfix (

When you attempt to add annotations, such as comments, to a cell in a scorecard that contains special characters, an error message appears.

This can occur even when a scorecard has been configured to accept annotations. The issue arises when a scorecard cell contains a number sign ("#") or a tilde ("~").


Workaround:   Remove the special characters from the scorecard and republish it to Monitoring Server.

The "Show Details" action in a scorecard that uses custom MDX to define target or actual KPI values displays the wrong data.

This can occur when you attempt to view details for a specific measure other than the default measure for a particular member in the Analysis Services cube. The "Show Details" action disregards the specific measure and displays data for the default measure.


Workaround:   None.

Help topics for dashboard elements in Dashboard Viewer for SharePoint Services are incomplete: spreadsheet reports and scorecards.

Web Parts Help files are not being updated, even though PerformancePoint Server 2007 SP2 has been installed.


Workaround:   Take one of the following steps:

·         Visit the Microsoft Office Online site ( for the most current documentation.

·         copy /Y
"%ProgramFiles%\Microsoft Office PerformancePoint Server\3.0\Monitoring\WebService\Preview\ppsDashboard.css"

 "%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\wpresources\Microsoft.PerformancePoint.Scorecards.WebParts\\ppsDashboard.css"

When you open a strategy map in Visio or Visio Viewer, the strategy map does not retain any filters that you applied.

In Visio or Visio Viewer, the strategy map displays data with no filters applied.


Workaround:   None.


Language Specific Known Issues

The following are language-specific known issues for PerformancePoint Monitoring.



Installation of a localized build of Monitoring Server after US-English has been installed causes ClickOnce to continue to use the US-English locale.

If you install a non-English localized build of Dashboard Designer after a US-English build has already been installed, ClickOnce will revert to the US-English locale.


Workaround:  Clear the ClickOnce cache before you start Dashboard Designer

To clear the ClickOnce cache:

1.      Navigate to the following Windows directory:  C:\Documents and Settings\[LoggedInUser]\Local Settings\Apps\2.0 where [LoggedInUser] is the user name of the user who is logged on to the computer.

2.      Delete all directories under C:\Documents and Settings\[LoggedInUser]\Local Settings\Apps\2.0).

Restart the ClickOnce installation, so that it opens with the correct locale settings.

When you open Dashboard Designer and try to view a SharePoint Lists data source, no data appears in columns that have non-ASCII text in the column names.

This is a known issue.

Some text strings, such as Updating, Stop, or filter strings, are not localized in the deployed dashboard.

Some text strings, such as Updating and Stop, which are seen in reports and scorecards that are refreshing for the purpose of displaying data, are not localized. In addition, filter options may not be localized in their drop-down lists. This occurs because the Web Controls or Web Parts that are deployed on the SharePoint site revert to English (language neutral assembly).


Workaround:   None.

Numeric formatting in KPIs and other dashboard elements may not honor the client locale.

When a KPI is created by using non-default numeric formatting (such as using periods for the thousands separator and commas for the decimal symbol) and is then used in the scorecard or other element, the formatting may change (to using commas for the thousands separator and periods for decimals). Similar behavior is seen with other scorecards and reports.


Workaround:   None.


Legal Notice

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 2008 Microsoft Corporation.  All rights reserved.

Microsoft, Excel, Hyper-V, PerformancePoint, PivotTable, PivotChart, SharePoint, Visio, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.