![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
If a calculated member is created as the child of a dimension other than "Measures", Excel can't see it. Why is that? Are there any other workarounds other than: 1. Use the new Add-in: Drawback...You have to create a 'report' wherein you limit what the user sees (and add in a new 'thing' they have to learn). 2. Change the cube structure to break out into individual 'real' measures what the dimension was 'breaking' out. Here is the MDX that works beautifully in the MDX Sample application: with member Type.SFF as 'sum( { type.type.sf, type.type.SO})' member Type.Cons as 'Iif(type.type.sf < type.type.SO, type.type.sf, type.type.so)' select non empty {type.type.so, type.type.sf , SFF, cons --, measures.consumed } on columns, non empty { [TimeWeek].[Week].members } on rows from productionplanning where [Itemid].[All Itemid].[17127] Any new ideas would be appreciated. Also, i admit i have not worked a lot with the New Excel add-in. But, from what i have seen so far I don't think it is a great fit for workers that aren't already pretty well skilled in the use of Excel's pivot tables. Do i need to get more familiar with it? |
#3
| |||
| |||
|
|
What version of Excel are you using? This was a by-design limitation on Excel 2000 which was changed in Excel XP. If using XP or 2003, you should be able to see them. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Steve" <sschneider (AT) grassusa (DOT) com> wrote in message news:%230C7OoPZEHA.1480 (AT) TK2MSFTNGP10 (DOT) phx.gbl... If a calculated member is created as the child of a dimension other than "Measures", Excel can't see it. Why is that? Are there any other workarounds other than: 1. Use the new Add-in: Drawback...You have to create a 'report' wherein you limit what the user sees (and add in a new 'thing' they have to learn). 2. Change the cube structure to break out into individual 'real' measures what the dimension was 'breaking' out. Here is the MDX that works beautifully in the MDX Sample application: with member Type.SFF as 'sum( { type.type.sf, type.type.SO})' member Type.Cons as 'Iif(type.type.sf < type.type.SO, type.type.sf, type.type.so)' select non empty {type.type.so, type.type.sf , SFF, cons --, measures.consumed } on columns, non empty { [TimeWeek].[Week].members } on rows from productionplanning where [Itemid].[All Itemid].[17127] Any new ideas would be appreciated. Also, i admit i have not worked a lot with the New Excel add-in. But, from what i have seen so far I don't think it is a great fit for workers that aren't already pretty well skilled in the use of Excel's pivot tables. Do i need to get more familiar with it? |
#4
| |||
| |||
|
|
I'm running Excel 2003 on WinXP. Also, as hinted, I've loaded the Cube Add-in. "Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote in message news:eqYyEKQZEHA.1764 (AT) TK2MSFTNGP10 (DOT) phx.gbl... What version of Excel are you using? This was a by-design limitation on Excel 2000 which was changed in Excel XP. If using XP or 2003, you should be able to see them. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Steve" <sschneider (AT) grassusa (DOT) com> wrote in message news:%230C7OoPZEHA.1480 (AT) TK2MSFTNGP10 (DOT) phx.gbl... If a calculated member is created as the child of a dimension other than "Measures", Excel can't see it. Why is that? Are there any other workarounds other than: 1. Use the new Add-in: Drawback...You have to create a 'report' wherein you limit what the user sees (and add in a new 'thing' they have to learn). 2. Change the cube structure to break out into individual 'real' measures what the dimension was 'breaking' out. Here is the MDX that works beautifully in the MDX Sample application: with member Type.SFF as 'sum( { type.type.sf, type.type.SO})' member Type.Cons as 'Iif(type.type.sf < type.type.SO, type.type.sf, type.type.so)' select non empty {type.type.so, type.type.sf , SFF, cons --, measures.consumed } on columns, non empty { [TimeWeek].[Week].members } on rows from productionplanning where [Itemid].[All Itemid].[17127] Any new ideas would be appreciated. Also, i admit i have not worked a lot with the New Excel add-in. But, from what i have seen so far I don't think it is a great fit for workers that aren't already pretty well skilled in the use of Excel's pivot tables. Do i need to get more familiar with it? |
#5
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |