Changing Column and Row Heading in MDX

I am trying to change the default row and column heading to make it more meaningful to the user in MDX. Can you please help me.

This is done easily in SQL like

SELECT the_actual_cost AS cost......

Thanks in advance.

Riju

You cannot use aliases in MDX. There are a couple of options though:
1) Select a "friendlier" member property to display instead of the name of the member.
2) Calculated members can be named on the fly.

.. there may be others in 2005 that im not aware of, but these are the ones i've traditionally used.

|||Hi,

Please try WITH SET/ WITH MEMBER option to name column headers.

Niyas|||AFAIK its impossible to retrieve the name of the named set (at least in adomd).|||Thank you all for responding to my question. I was able to rename the column header using calcualted member. However, i am little concerned about the efficiency of this technique. For example i have a measure [date of transaction] and if i want it to be named simply as [date] i have to do [date] as '[date of transaction]'. I am wondering if this will result in slower queries response time?

Thanks
Riju
|||

Why dont you just rename your measure (provided you dont already have a lot of stuff running against this measure)?

|||Hi Peter,

I am using one measure in multiple reports and trying to give them different names in different reports to make it more meaningful.

Thanks
Riju|||

Then calculated members may be the only way..

Changing Column and Row Heading in MDX

I am trying to change the default row and column heading to make it more meaningful to the user in MDX. Can you please help me.

This is done easily in SQL like

SELECT the_actual_cost AS cost......

Thanks in advance.

Riju

You cannot use aliases in MDX. There are a couple of options though:
1) Select a "friendlier" member property to display instead of the name of the member.
2) Calculated members can be named on the fly.

.. there may be others in 2005 that im not aware of, but these are the ones i've traditionally used.

|||Hi,

Please try WITH SET/ WITH MEMBER option to name column headers.

Niyas|||AFAIK its impossible to retrieve the name of the named set (at least in adomd).|||Thank you all for responding to my question. I was able to rename the column header using calcualted member. However, i am little concerned about the efficiency of this technique. For example i have a measure [date of transaction] and if i want it to be named simply as [date] i have to do [date] as '[date of transaction]'. I am wondering if this will result in slower queries response time?

Thanks
Riju
|||

Why dont you just rename your measure (provided you dont already have a lot of stuff running against this measure)?

|||Hi Peter,

I am using one measure in multiple reports and trying to give them different names in different reports to make it more meaningful.

Thanks
Riju|||

Then calculated members may be the only way..

Changes to MDX when upgrading to AS 2005

I was wondering if anybody has upgraded to AS 2005 without having to change
their stored MDX extensively to work with the new AS model. The company I
work for has 100's of reports with 100's of MDX queries that might
potentially need to be updated because 1) it's just not possible to do things
the old way and 2) we want to utilize the new features of SSAS 2005.
I'm looking for general advice or maybe some good things to know when
upgrading to SSAS 2005 while using SSRS 2005 as your enterprise reporting
framework.
Thanks,
Joshhavent got anything definitive, other than to say our mdx based reports
ported fine. Only issue was 2005 was stricter with having links in page
footers which caused a warning in 2000 but wouldnt work in 2005
"JSI" <JSI@.discussions.microsoft.com> wrote in message
news:B909920B-124C-4B09-B584-2EF40847F3B6@.microsoft.com...
>I was wondering if anybody has upgraded to AS 2005 without having to change
> their stored MDX extensively to work with the new AS model. The company I
> work for has 100's of reports with 100's of MDX queries that might
> potentially need to be updated because 1) it's just not possible to do
> things
> the old way and 2) we want to utilize the new features of SSAS 2005.
> I'm looking for general advice or maybe some good things to know when
> upgrading to SSAS 2005 while using SSRS 2005 as your enterprise reporting
> framework.
> Thanks,
> Josh