I typically don’t implement a Relative Date dimension in Tabular. Instead, I flatten time calculations in measures, such as SalesAmountYTD, SalesAmountQTD, etc. There are a lot of formulas to duplicate but it’s not that bad.

First of all, great solution – I’m an analysis services newbie but this works well and was easy to implement, although I had the issue of measure not aggregating when you use the dates hierarchy exclusively also.

For example if you browsed the cube using the date hierarchy for the default member (current day) the value displayed would be the aggregation of both the values at the intersection the default date member, [Relative Dates].&[1] AND the [Relative Dates].[Current Date] members (assuming that my relative dates dimension only contained the two members) – I could only assume this is because while we set the relative dates member to hide if there was ‘no name’ the member is still included in the cube and is included in aggregations accordingly.

The only way I could find to get around this was to include another ‘no name’ member in the relative dates dimension ([Relative Dates].&[2]) that served as a ‘balancing member’ to ensure that the amount displayed when the date hierarchy was used without relative time. See below for code.

–Create Balancing Amounts

Scope ([Relative Time].&[2], [Calendar].[Financial Calendar].ALLMEMBERS);

this = AGGREGATE(EXCEPT([Relative Time].[Relative Time].[All].Children,[Relative Time].[Relative Time].[Relative Time Name].&[1]))*-1;

End Scope;

Am I missing something? Can I ask how did you manage to get around this issue.

Thanks very much

I would like your help in implementing the Relative Date dimension.
I am getting an issue with the MDX Programming –section…

Would you be able to let me know what you did to get it to work?

Kind regards,

P3L