Update the CURRENTPERIOD for a Model

Every PerformancePoint Model has a CURRENTPERIOD property. So why set the CURRENTPERIOD property? You don't have to set this property but here is some basic functionality that it can provide:

• Dynamically update the data or date range for a Form or a Report
• Set the date range for Cycle
• Use it as a variable in a PerformancePoint Rule

Go to the model that you want to set the CURRENTPERIOD for and then check out the model. In this example we are going to set the CURRENTPERIOD for an Exchange Rate model so that we can build a PerformancePoint form with a dynamic date range:

Select Schedule Current Period Updates... from the workspace action pane:

The CURRENTPERIOD is presently set December FY 2009 but we want it to be July FY 2009 which is the first period of the budget fiscal year in our PerformancePoint Application. First click Remove Last to remove the existing CURRENTPERIOD . Now click on the ellipsis to set the CURRENTPERIOD. Select the correct date and press OK.

Now select the single chevron (>) to copy the CURRENTPERIOD value to the Update Schedule section:

You can actually schedule multiple CURRENTPERIOD values which are updated based on the update time. In this case we are only going to set one CURRENTPERIOD. Click OK and then save the model. Now we can use the CURRENTPERIOD value. In order to update the of the CURRENTPERIOD in the form I am building, I need to Refresh System data as shown below:

Now I can set a dynamic date range for the Time Dimension:

Select Add Dynamic Range... . In this case I am going to set the Start of Range to 0 and the End of Range to 11 (0 to 11 represents 12 periods). Next Click OK and then OK again. The form will now dynamically display the Time members based on the CURRENTPERIOD. Refresh the form to update the time members

Here is form that I created suing the CURRENTPERIOD. Notice that the first time member is July FY 2009 which is equal to the CURRENTPERIOD and that the last member is June FY 2009 which equals CURRENTPERID + 11.

Troy

Technorati Tags: performancepoint, sqlserver, analysis, microsoft, planning