Duplication of KPI's within PPS

Has anyone ever come up with the of duplication of KPI related information after dragging and dropping two seperate KPI's within a scorecard......... well! I have. Now the issue is quite simple, I define two separate KPI's called KPI1 and KPI2. I define KPI1 in the following manner:

After this step I define KPI2 in the following manner:

Once I perform the following operations I basically define a scorecard dropping a dimension (eg: Brand) for this purpose and then drag KPI1 and then KPI2 (Note: KPI2 is the sibling of KPI1). The scorecard gets generated in the following fashion:
Now if you notice the scorecard the Actual and Target is repeated for KPI2 even though KPI2 has the names defined as Test1 and Test2 respectively and the default values for KPI2 is empty for all rows of the slicing dimension. This issue is due to the fact that PPS did not recognize KPI2 as a valid sibling of KPI1 (This is indeed an issue with PPS and needs to be changed as soon as possible in the future version) because of the name given to the Actual and Target in KPI2 (defined as Test1 and Test2 respectively). To overcome this issue in the scorecard, the best option to follow is to keep the names the same across for all the KPI's. In this case let us change the KPI2 in the following manner:
Once this is done after adding both the KPI's to the scorecard, right click on the KPI name within the scorecard and navigate to the metric setting and change the name to Test1 and Test2 respectively for Actual and Target as shown in the following screenshots:
(Once the metric setting is selected change the name as shown below)
Change Actual to Test1 and Target to Test 2 respectively and as the saying goes--> when the going gets tough, the tough get going. The scorecard is perfectly represented as it ought to.
Another Issue I run into is the connection problem with Excel services as a source. Some excel connections work with the same service account and others do not even though the permissions are the same. Well I sort of know a way to solve the issue.... but let me tell this story some other time.

Comments

Post a Comment

Popular posts from this blog

Load Data into Azure DW using C# in an SSIS script task

Image
Now there are a lot of reasons why SSIS needs to be leveraged for loading data into the Azure DW platform. Even though Polybase and Azure Data factory are the core criteria's, here are the templates for the SSIS script task that were leveraged to load data (full and incremental into Azure DW) for a specific customer rather than using the data flow task: SSIS Full Load script : SSIS Incremental Load script : There are a few reasons for this approach and one of them being that the existing package was using a similar structure and one not to be deviated from. The other being that some key logging aspects needed to be handled in a Legacy platform that could not be decommissioned at that time.
Read more

Branding your SharePoint site in a super fast way - Emgage

Branding a SharePoint farm on premise or in O365 is an extremely time absorbing task. Recently found a few tools called emgage prime and emgage turbo which basically gives you customized UX branding solutions to make you get to what you want super fast and super easy....Just used it on a SP2016 farm a few days ago and the results were tremendous. A definite recommendation on the SP side of things.
Read more

Power BI To Embed Or Not To Embed

It is very critical for organizations to work & play with data. Power BI - the reporting solution from Microsoft is literally scorching the market with its rapid pace in usage. On a quick note while interacting with your Power BI report like the following--> This report is accessible by the public. In order to create a more personalized/advanced security reporting structure with Power BI, the Power BI embedded would be the way to go. Create a workspace collection in Azure and then generate the required API keys (two by default - primary and secondary). These API keys will be leveraged by your web application. Once this is done create the pbix solution file in your desktop tool and publish or import the pbix solution to the Azure workspace using powershell/C#/ruby/java etc... Now to interact with the pbix file in your application, you need to leverage the Power BI Embed API's. However there is another approach using Power BI API's instead of the embed API's. The em
Read more