Ramifications of Changing the Name and Label of a Dimension Member
Posted by Alan on August 9, 2008
Almost every component of PerformancePoint Planning (Applications, Model Sites, Dimensions, Cycles, Jobs, etc.) allows you to change the value in the “Name” field but not the “Label” field. At a database level, “Label” is your unique identifier. Now I personally have always thought that the PPS team got this backwards and that “Name” should be the unique ID and “Label” should be the changeable field, but they never bothered to ask me, so I guess we just have to go with it….
Now when it comes to Dimension Members they are treated a little differently. You can change the value in either the “Name” or “Label” fields even after you have created and deployed your Model, created an Input Form, begun a Cycle and started submitting data.
At a first glance, this seems to be a great thing. Being able to modify the value in the “Label” field gives you ultimate flexibility to modify your structure as your organization changes over the course of time . When you make a change, after you re-deploy your model when you open up your forms or reports, the new names are displayed.
However, there is an ugly downside to this flexibility. If on your forms/reports you have included a filter, that filter will cease to work if one of the values in the filter has had its “Label” changed — basically the filter is now looking for something that does not exist anymore. In addition, any custom created MDX rules that you have created will also cease to function. Both of these will have to be re-worked in order for your Model to function properly.
Ultimatley remember this — a change to a “Label” done in the PerformancePoint Planning Business Modeler does not roll-down to forms or rules, so be very careful and think it through before you ever change a Dimension Member’s Label.