The values returned for a calculated measure that references a time series MDX function might not display the expected values when you have more than one hierarchy defined to the Time dimension.

For example, say you have defined a calculated measure using the following MDX:

For your Time dimension, you have two hierarchies defined: Year-Quarter-Month and Year-Month-Day, where Year-Quarter-Month is the default hierarchy. In the current view of the cube, you are referencing the other Time hierarchy, Year-Month-Day. In this scenario, the values displayed for the calculated measure as you drill down into Year-Month-Day might not be what you expect.

Specifically, when you display the Year-Month-Day hierarchy, the expression [Time].currentmember actually resolves to [Time].[default_hierarchy].currentmember. Recall that the default hierarchy is Year-Quarter-Month. The current member for Year-Quarter-Month is the All member. So, the All member value is returned for every member of the Year-Month-Day hierarchy. In this example, the expression resolves to:

To ensure that the correct value of [Time].currentmember is returned in your query, you must define your calculated measure to consider all hierarchies in the Time dimension and test to see which hierarchy is currently displayed.

Continuing with the current example, you could modify the MDX expression for your calculated measure to the following:

Operating System and Release Information