Also, be aware that when the measures are changed, the
Name field does not change, and therefore still contains the name of the first measure.
It??™s important that developers remember to change this before moving forward.
The next step in the process is to optionally add measure filters. Measure filters
are a way of selecting a member from a dimension that will limit what is seen in
the value of the KPI and can be set for both the Actual and Target measures. As an
example, this KPI might be for a particular product line. Therefore, selecting the
checkbox to add measure filters allows the developer to choose a dimension.
Figure 5-8 These are the two views for adding new KPIs. The top view creates a KPI in
PerformancePoint based on cube measures. The bottom view imports KPIs
that are part of a cube in Analysis Services 2005.
94 B u s i n e s s I n t e l l i g e n c e w i t h M i c r o s o f t O f f i c e P e r f o r m a n c e P o i n t S e r v e r 2 0 0 7
In the case of the Adventure Works database, the Product dimension could be used to
help filter the members. If the Product.Product Model Lines hierarchy was chosen,
then both the Actual and Target could be set to Mountain to narrow the focus of this
particular KPI down to the just products in the Mountain product line. While the
wizard lets developers make specific selections of members from a dimension, these
selections can also be made dynamic, which will be discussed later in the chapter.
The next step of the wizard allows the developer to add columns based on
members from a dimension.
Pages:
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147