1. Download the following file and extract the DecompositionTree.xap file. (DecompositionTree.zip)
2. Log on to your SharePoint servers and navigate to the following file location:
   1. C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\PPSWebParts
3. Paste the DecompositionTree.xap file into this folder and replace the one that is already there.
4. IISReset the server.
5. Test.

 No filter data retrieved

The error may happen when you have the Per-user Identity setting enabled in the data connection settings:

When using Per-user Identity, Kerberos authentication is used to connect to the data source. There is a Kerberos hotfix that resolves this error:

https://support.microsoft.com/en-us/kb/969083

The hotfix needs to be applied to the SharePoint server running PerformancePoint Services and on the SQL Server database server that hosts the data source.

You are using PerformancePoint 2013 and Dashboard Designer 2013 to make scorecards.  On those scorecards you want to not show grid lines and you want to change the default font color.  All works and looks fine in Dashboard Designer but when you upload to SharePoint 2013 the grid lines still show and the font color has not changed.

Workaround:

PerformancePoint's implementation of SharePoint themes caused this issue, you can work around this issue by making a small change to a PerformancePoint style sheet.

1. Make a backup copy of this file:  (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\1033\STYLES\Themable\performancepoint.css)
2. Open the file from step 1 in notepad, all of the text is on one super long line so it will be difficult to read.
3. Search for this text:  table.sctb th.scc,table.sctb td.scc{/* [ReplaceColor(themeColor:"Lines")] */ border-color:#ababab;border-width:1px;border-style:solid;color:inherit !Important;}
4. Replace above text with this:  table.sctb th.scc, table.sctb td.scc {border-color: #ababab;}
5. Save the file
6. Reload the scorecard with your web browser  (if set to not show grid lines, they will not show, and the font color will match whatever color was set in Dashboard Designer)

This issue maybe resolved in a future release of the product.

With Internet Explorer 10, when the zoom level is not set to 100%, and viewing PerformancePoint 2010 dashboard page with a large filter, the filter dropdown does not display entirely (cannot see or select some items that are in the filter list).

We have seen this issue with SharePoint 2010, but you could encounter this issue with newer or older versions of SharePoint and Internet Explorer as well.

Cause

By default, the web page may be loading in the Internet Explorer 8 (or other) document mode.

Workaround

Change the document mode to Internet Explorer 10 mode in developer tools.

To do this:

1. Open the PerformancePoint Services dashboard page in Internet Explorer.
2. Press F12 on your keyboard to bring up the Developer Tools at the bottom of your browser.

3. Click the Edge document mode dropdown in the top right corner of the Developer Tools.

4. Select 10 (or you may need to experiment with other settings here).

This will restore the functionality of the filter dropdowns. 

In some cases, Dashboard Designer for PerformancePoint Services 2010 will not launch if you go to the PerformancePoint Services page and click on "Run Dashboard Designer".

Cause

In some cases, the cause of this is that the master page for both the Site Master Page and the System Master Page for the BI site is not set to v4.master.

Workaround

In this scenario, the resolution is to set the Site Master Page and the System Master Page for the BI site to use v4.master, and then Dashboard Designer for PerformancePoint Services 2010 will launch.

You can do this in Site Settings > Master Page.

Also, the user launching Dashboard Designer needs to be in the local Administrators group on their local machine.

There are a number of different types of data sources that we can create in PerformancePoint Services Dashboard Designer, and a number of different ways of creating them.

This article describes a way in which we can create a new Analysis Services data source in Dashboard Designer using per-user identity, and some steps for setting up the Kerberos constrained delegation that is required in order for it to work.

These are general steps for a typical environment, but they work well in the majority of cases.

Part 1 – Gather the information

Here is some sample environment information.

1. The account that is running PerformancePoint Services Application Pool is:  svcPPS
2. The name of the SharePoint Server where PerformancePoint Services is running is:   APP01
3. The account that is running the Claims-To-Windows-Token-Service is:   svcClaims
4. The name of the SharePoint Server where the Claims-To-Windows-Token-Service is running is:   APP01
5. The account that is running the Analysis Services instance that we are making the new data source connection to using per-user identity is:  svcSSAS
6. The name of the Analysis Services server that we are making the new data source connection to using per-user identity is:   SSAS01
7. The FQDN naming for domain objects is:   contoso.com

Part 2 – Set the SPNs in Active Directory

Based on our environment information above, below are the SPNs that we need set in Active Directory.

• NOTE 1: You will need to do these at a PowerShell command prompt on a Domain Controller.
• NOTE 2: Copy and paste sometimes does not work with these, so you may need to type them in manually.
• NOTE 3: The first 2 SPNs below are not valid SPNs. They are applied to the specified service accounts in order to reveal the delegation options in the AD users and computers add-in.
• NOTE 4: Using -s rather than -a will check for duplicate SPNs before adding that SPN.

1. setspn - a PPS/APP01 svcPPS
2. setspn - a CTWTS/APP01 svcClaims
3. setspn - a MSOLAPSVC.3/SSAS01 svcSSAS
4. setspn - a MSOLAPSVC.3/SSAS01.contoso.com svcSSAS

Part 3: – Configure constrained delegation

Once the SPNs have been added in Active Directory, then we will need to configure constrained delegation for the PerformancePoint Services account, and for the Claims-To-Windows-Token-Service account.

Below are general steps for doing that.

1. In Active Directory Users and Computers > svcPPS > Properties > Delegation Tab > Trust this user for delegation to specified services only > Use any authentication protocol > Add > Users or Computers > svcSSAS > Check Names > OK > “Select All” Available Services > OK > OK.
2. In Active Directory Users and Computers > svcClaims > Properties > Delegation Tab > Trust this user for delegation to specified services only > Use any authentication protocol > Add > Users or Computers > svcSSAS > Check Names > OK > “Select All” Available Services > OK > OK.

Part 4: – Make sure Claims-To-Windows-Token-Service setup is complete

Since the Claims-To-Windows-Token-Service is involved in the Kerberos constrained delegation process, the account that is running the Claims-To-Windows-Token-Service needs to have certain permissions on the SharePoint servers where the Claims-To-Windows-Token-Service is running. 

Make sure that the account that is running the Claims-To-Windows-Token-Service (svcClaims in my sample environment information above) has the permissions below on ALL of the SharePoint servers where the Claims-To-Windows-Token-Service is running. 

1. Must be in the local Administrators group
2. In the server’s local security policy (Start > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment), the Claims-To-Windows-Token-Service account needs to have these permissions:
1. Act as part of the operating system
2. Impersonate a client after authentication
3. Log on as a service

Part 5: – Testing

After all of the steps above have been completed, there may be an Active Directory replication delay before we are able to create a new Analysis Services data source in Dashboard Designer using per-user identity, but sometimes it will start working right away. If it doesn’t start working right away, wait for a little while for Active Directory replications to happen (or force it), and then close and reopen Dashboard Designer and try it again.