Olap and reporting service problem

Hi.
This is an OLAP question.
I have a dimension which is a father-son dimension.
I built the cube in analysis server.
In the analysis browser I can see the dimension fine,
I hant my reporting services report to show that dimension.
The problem is that the report won't show me that dimension in
hierarchy tree (even if I check drill down) but flatten it down.
Does some one know if report service can handle those kind of reports?
Thanks.Hi Nick,
I am having the same problem. Have you managed to get an answer? Would love
to know how to solve this.
Anusha
"nicknack" wrote:
> Hi.
> This is an OLAP question.
> I have a dimension which is a father-son dimension.
> I built the cube in analysis server.
> In the analysis browser I can see the dimension fine,
> I hant my reporting services report to show that dimension.
> The problem is that the report won't show me that dimension in
> hierarchy tree (even if I check drill down) but flatten it down.
> Does some one know if report service can handle those kind of reports?
>
> Thanks.
>|||Hi Anusha,
I did managed to get an answer.
You can't do this!
RS is not really an OLAP tool and it doesn't know how to deal with
parent-child dimension and thats why it flatten down the dimension.
Currently, I saw that there isn't any simple way to solve this.
Sorry...
Anusha =D7=9B=D7=AA=D7=91:
> Hi Nick,
> I am having the same problem. Have you managed to get an answer? Would lo=ve
> to know how to solve this.
> Anusha
> "nicknack" wrote:
> > Hi.
> > This is an OLAP question.
> >
> > I have a dimension which is a father-son dimension.
> > I built the cube in analysis server.
> > In the analysis browser I can see the dimension fine,
> >
> > I hant my reporting services report to show that dimension.
> > The problem is that the report won't show me that dimension in
> > hierarchy tree (even if I check drill down) but flatten it down.
> >
> > Does some one know if report service can handle those kind of reports?
> >
> >
> > Thanks.
> >
> >|||Thanks, At least I can stop pulling my hair out!!!
Anusha
"nicknack" wrote:
> Hi Anusha,
> I did managed to get an answer.
> You can't do this!
> RS is not really an OLAP tool and it doesn't know how to deal with
> parent-child dimension and thats why it flatten down the dimension.
>
> Currently, I saw that there isn't any simple way to solve this.
> Sorry...
> Anusha ×?ת×?:
> > Hi Nick,
> >
> > I am having the same problem. Have you managed to get an answer? Would love
> > to know how to solve this.
> >
> > Anusha
> >
> > "nicknack" wrote:
> >
> > > Hi.
> > > This is an OLAP question.
> > >
> > > I have a dimension which is a father-son dimension.
> > > I built the cube in analysis server.
> > > In the analysis browser I can see the dimension fine,
> > >
> > > I hant my reporting services report to show that dimension.
> > > The problem is that the report won't show me that dimension in
> > > hierarchy tree (even if I check drill down) but flatten it down.
> > >
> > > Does some one know if report service can handle those kind of reports?
> > >
> > >
> > > Thanks.
> > >
> > >
>sql

olap and hierarchy problem

Hi.
This is an OLAP question.

I have a dimension which is a father-son dimension.
I built the cube in analysis server.
In the analysis browser I can see the dimension fine,

I hant my reporting services report to show that dimension.
The problem is that the report won't show me that dimension in hierarchy tree (even if I check drill down) but flatten it down.

Does some one know if report service can handle those kind of reports?

Thanks.I assume the dimension is a parent-child dimension. RS is not an OLAP browser. As you have noticed, it flattens the parent-child dimenion. In this presentation download, you will find two approaches for dealing with parent-child dimensions in RS. The first one uses the RS recursive support. The second bypasses the SSAS 2005 provider in order to use straight MDX to expand the hierarchy. Needless to say, both approaches have their limitations and we can expect the support of parent-child dimensions and UDM in general to improve in future releases.|||Hi Teo,
Thanks for your replay, Its hard to find help and support for Olap and for Olap and SSRS on the net.

Its very disappointing to hear that RS does not support OLAP (and for me, if it can't handle parent-child dimension it can't handle olap).

Looks like we will have to use some other programs for working with cubes and creating reports.

Thanks for your post and I will have a look at the link you supplied to check if by any chance there is a way to work with parent-child with out any work arounds.

Regards,
Roy.|||Just to clarify. I didn't say it doesn't support OLAP. I said that it flattens the parent-child hierachies when converting them to two-dimensional datasets.|||I know you didn't - I did ("and for me, if it can't handle

parent-child dimension it can't handle olap").

I think Its a must when working with olap.

Thank for the reply :)
|||

How would you go about using OLAP with SSRS?

Do you purchase OLAP?

I've seen it used, but I know little to nothing about it.

|||You can build OLAP solutions (cubes) with analysis services and then deploy the cube to the analysis server.

After that you can create a report and as a data source tell him to connect to the cube on the analysis server.

But as you can see, reporting services can really work with olap :(

OLAP 2005 Calculated Measure using Field/Dimension

I am building an OLAP Cube off someone else's data model, so i am a bit stuck trying to decision off model decisions already made and being used.

They have a field for Satisfaction which has the value Yes, No, and Blank when no survey result was received.

I need to make a satisfaction percent based on (count of Yes) / (count of Yes + count of No). So i do not count blank when no result was received.

I need the caculated measure to work against all of the dimensions, so i do not want to build such a specific MDX code that it only works with Time, for example.

Help will be extremely Appreciated

*A

If there is a Satisfaction dimension/attribute, with the members above: Yes, No, and Blank, and a cube "count" measure like SurveyCount, then does something like this work:

([Measures].[SurveyCount], [Satisafaction].[Satisfaction].[Yes])/

(([Measures].[SurveyCount], [Satisafaction].[Satisfaction].[Yes])

+ ([Measures].[SurveyCount], [Satisafaction].[Satisfaction].[No]))

|||WORKED GREAT AND WAS REALLY EASY TO UNDERSTAND AND CHANGE FOR OTHER USES!!!!!!!sql

OLAP 2005 Calculated Measure using Field/Dimension

I am building an OLAP Cube off someone else's data model, so i am a bit stuck trying to decision off model decisions already made and being used.

They have a field for Satisfaction which has the value Yes, No, and Blank when no survey result was received.

I need to make a satisfaction percent based on (count of Yes) / (count of Yes + count of No). So i do not count blank when no result was received.

I need the caculated measure to work against all of the dimensions, so i do not want to build such a specific MDX code that it only works with Time, for example.

Help will be extremely Appreciated

*A

If there is a Satisfaction dimension/attribute, with the members above: Yes, No, and Blank, and a cube "count" measure like SurveyCount, then does something like this work:

([Measures].[SurveyCount], [Satisafaction].[Satisfaction].[Yes])/

(([Measures].[SurveyCount], [Satisafaction].[Satisfaction].[Yes])

+ ([Measures].[SurveyCount], [Satisafaction].[Satisfaction].[No]))

|||WORKED GREAT AND WAS REALLY EASY TO UNDERSTAND AND CHANGE FOR OTHER USES!!!!!!!

OLAP - EXCEL problem - urgent

Hello,

I have a dimension hierarchy with 2 levels, like this:

A - X

- Y

- Z

B - U

- V

- T

And I have a cube with the dimension above and one measure (sum).

The fact table of this cube has 2 columns (level2,sumvalue) and i have the values:

Level2 SumValue

X 1

Y 2

T 6

When I access this cube from Excel and use multiple selection weird stuff happends.

So, I create a Pivot table, in which i select only X,Y,U:

Level1

Level2

Total

A

X

1

Y

2

A Total

3

Grand Total

3

If i give a refersh to this pivot table i get :

SumValue

Level1

Level2

Total

A

X

1

Y

2

A Total

3

B

6

Grand Total

9

Why i see the B in the pivot table, if i selected only X,Y,U and U has no value in the fact table? I need an urgent answer because end-users use a lot the refresh option and in this case they see wrong values.

I'm using Microsoft Analysis Server build 9.00.2153 (SP1) and Microsoft Office Excel 2003 (11.6560.6568) SP2. I made the test with Microsoft Analysis Server SP2 and same version of Excel and i got the same result.

Any help will be appreciated.

Thanks,

Vulcano

A couple of things to check, that I can think of:

Is "Visual Totals" still enabled after refresh (ie. "Totals include Hidden Items" is disabled) - otherwise, these results would be expected?|||Thanks Deepak for your answer.

The property of the pivot table "Include hidden members in totals" is disable all the time. So no hidden members are included. In my dimension i don't have hidden members.

I run a Profiler and I discovered something strange:

For the first pivot table the query shown in the Profiler is :

SELECT NON EMPTY HIERARCHIZE(Except({AddCalculatedMembers(Except({AddCalculatedMembers({DrillDownMember({DrillDownLevel({[Dimension].[Hierarchy].[All]})}, {[Dimension].[Hierarchy].[Level1].[T] , [Dimension].[Hierarchy].[Level1].[ V ] })})}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] }))}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] })) DIMENSION PROPERTIES PARENT_UNIQUE_NAME ON COLUMNS FROM [TestWarTestSimple] WHERE ([Measures].[SumValue])

For the second pivot table when the refresh is done the query is:

SELECT NON EMPTY HIERARCHIZE(Except({AddCalculatedMembers(Except({AddCalculatedMembers({DrillDownMember({DrillDownLevel({[Dimension].[Hierarchy].[All]})}, {[Dimension].[Hierarchy].[Level1].[ T ] })})}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] }))}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] })) DIMENSION PROPERTIES PARENT_UNIQUE_NAME ON COLUMNS FROM [TestWarTestSimple] WHERE ([Measures].[SumValue])

Why the two queries are different? Why in the second query [Dimension].[Hierarchy].[Level1].[ B ] disappears?

Thanks,

Vulcano|||

The member which disappeared in the 2nd query is: [Dimension].[Hierarchy].[Level1].[ V ] , not [Dimension].[Hierarchy].[Level1].[ B ] (though maybe these are place-holder, not real, names?).

When you look at the drop-down list of members selected in the pivot table, do you find that this missing member is now selected? If so, this could be a side-effect of refreshing the pivot table (though I'm not sure why the refresh would change the selected members).

|||

My mistake Deepak, the queries are wrong, they are missing the A, B Members of the dimension. I post again the queries:

For the first pivot table the query shown in the Profiler is :

SELECT NON EMPTY HIERARCHIZE(Except({AddCalculatedMembers(Except({AddCalculatedMembers({DrillDownMember({DrillDownLevel({[Dimension].[Hierarchy].[All]})}, {[Dimension].[Hierarchy].[Level1].[ A ] , [Dimension].[Hierarchy].[Level1].[ B ] })})}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] }))}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] })) DIMENSION PROPERTIES PARENT_UNIQUE_NAME ON COLUMNS FROM [TestWarTestSimple] WHERE ([Measures].[SumValue])

For the second pivot table when the refresh is done the query is:

SELECT NON EMPTY HIERARCHIZE(Except({AddCalculatedMembers(Except({AddCalculatedMembers({DrillDownMember({DrillDownLevel({[Dimension].[Hierarchy].[All]})}, {[Dimension].[Hierarchy].[Level1].[ A ] })})}, {[Dimension].[Hierarchy].[Level2].[V], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] }))}, {[Dimension].[Hierarchy].[Level2].[ V ], [Dimension].[Hierarchy].[Level2].[T], [Dimension].[Hierarchy].[Level2].[ Z ] })) DIMENSION PROPERTIES PARENT_UNIQUE_NAME ON COLUMNS FROM [TestWarTestSimple] WHERE ([Measures].[SumValue])

And you are right again: when the first pivot is created the X,Y,U members are selected, after the pivot is refresh the U member is not selected anymore ( so the member selected are X,Y,B). Is this the right behaviour, or maybe is a bug?

Thanks,Vulcano

OLAP - Dimension

Hi Folks,

We have problems with our Cube.
One of our dimension has more 64K (64,000) members.

We had tried to use grouping but it does not meet our needs.
Can somebody suggest another way to to resolve this limitation problem besides grouping.
Any comments/suggestion (even redesigning the dimension or fact tables) will be welcome.

Thanks and have a great day.This is a big question, can you post the DDL of the mart/warehouse that includes all dim tables and the fact table? If you are storing measures at the dim level you might be able to store them in the fact.|||Hi There,
i have this strong feeling that you can solve this problme by createing a groups on top of your dimension, but one thing every time you need to rebuild this dimension rather then just by increnmental update, rebuild it every time when you process the cube. becuase i have also got the same problem and i am doing the same.

Thanks
Pawan
Originally posted by REVI
Hi Folks,

We have problems with our Cube.
One of our dimension has more 64K (64,000) members.

We had tried to use grouping but it does not meet our needs.
Can somebody suggest another way to to resolve this limitation problem besides grouping.
Any comments/suggestion (even redesigning the dimension or fact tables) will be welcome.

Thanks and have a great day.|||Hi,

This is the DDL:

CREATE TABLE [dbo].[Dim_FII_Code] (
[FII_Code_SID] [int] NOT NULL ,
[FII_Code_Value] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FII_Code_Description] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FII_Code_Group] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

CREATE TABLE [dbo].[Dim_Account] (
[Account_SID] [int] NOT NULL ,
[Account_Code] [nvarchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Name] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Industry_Code] [nchar] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Industry_Desc] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Start_Date] [datetime] NULL ,
[Account_Term_Date] [datetime] NULL ,
[Account_Country_Code] [nchar] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Country_Desc] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_State_Code] [nchar] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_State_Desc] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_City] [nvarchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Zip_Code] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[HQ_DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Domestic_Ultimate_DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Global_Ultimate_DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Fact_ID] [int] NULL ,
[Fact_Name] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SIC_Code] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Global_4000_Company_Flag] [char] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Type_Group] [nchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Type] [nchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Sales_Region_Code] [nchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Sales_Territory_Code] [nchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Service_Code] [nchar] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Service_Desc] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

CREATE TABLE [dbo].[Dim_Date] (
[Date_SID] [int] NOT NULL ,
[Month_SID] [int] NOT NULL ,
[Day] [datetime] NULL ,
[Day_of_Week] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Weekday_Flag] [char] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

CREATE TABLE [dbo].[Fact_Search_FII_Code_Usage] (
[Account_SID] [int] NOT NULL ,
[Date_SID] [int] NOT NULL ,
[FII_Code_SID] [int] NOT NULL ,
[Total_Search_Qty] [int] NULL ,
[No_Headline_Search_Qty] [int] NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

We countering problems with Dim_FII_Code, the members for the
exceed for the fii_code_group. It is more than 64k.

Another thing, can you explain how grouping work.
One data model without grouping and with grouping will help.

Thanks and have a nice day.|||Originally posted by pawan
Hi There,
i have this strong feeling that you can solve this problme by createing a groups on top of your dimension, but one thing every time you need to rebuild this dimension rather then just by increnmental update, rebuild it every time when you process the cube. becuase i have also got the same problem and i am doing the same.

Thanks
Pawan

HI ,

Can you explain how grouping work.
One data model without grouping and with grouping will help.

Thanks and have a nice day.|||Hi There,
what you can do that, create a Hierarchical dimension like Data_created and under that the sub member is your 64k dimension which is Dim_FII_Code. one thing don't take the full date just extracte year out of that date field and create one more field in your table called "Dim_FII_Code" i assume so and update that field with this year value. Then go back to your cube and create a Hierarchical dim as YEAR
by using newly created field which is having year value and sub member is Dim_FII_Code. But make sure that this field is not null.
if you have any ? then do mail to this address.
pawan.bhatnagar@.aut.ac.nz

Thanks
Pawan

[Originally posted by REVI
Hi,

This is the DDL:

CREATE TABLE [dbo].[Dim_FII_Code] (
[FII_Code_SID] [int] NOT NULL ,
[FII_Code_Value] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FII_Code_Description] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[FII_Code_Group] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

CREATE TABLE [dbo].[Dim_Account] (
[Account_SID] [int] NOT NULL ,
[Account_Code] [nvarchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Name] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Industry_Code] [nchar] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Industry_Desc] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Start_Date] [datetime] NULL ,
[Account_Term_Date] [datetime] NULL ,
[Account_Country_Code] [nchar] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Country_Desc] [nvarchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_State_Code] [nchar] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_State_Desc] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_City] [nvarchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Zip_Code] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[HQ_DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Domestic_Ultimate_DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Global_Ultimate_DUNS_Number] [nchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Fact_ID] [int] NULL ,
[Fact_Name] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[SIC_Code] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Global_4000_Company_Flag] [char] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Type_Group] [nchar] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Account_Type] [nchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Sales_Region_Code] [nchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Sales_Territory_Code] [nchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Service_Code] [nchar] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Service_Desc] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

CREATE TABLE [dbo].[Dim_Date] (
[Date_SID] [int] NOT NULL ,
[Month_SID] [int] NOT NULL ,
[Day] [datetime] NULL ,
[Day_of_Week] [nvarchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Weekday_Flag] [char] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

CREATE TABLE [dbo].[Fact_Search_FII_Code_Usage] (
[Account_SID] [int] NOT NULL ,
[Date_SID] [int] NOT NULL ,
[FII_Code_SID] [int] NOT NULL ,
[Total_Search_Qty] [int] NULL ,
[No_Headline_Search_Qty] [int] NULL ,
[Date_Created] [datetime] NULL ,
[Date_Updated] [datetime] NULL
) ON [PRIMARY]
GO

We countering problems with Dim_FII_Code, the members for the
exceed for the fii_code_group. It is more than 64k.

Another thing, can you explain how grouping work.
One data model without grouping and with grouping will help.

Thanks and have a nice day.sql

OLAP

If I paste a dimension in excel (import data) per default all data is
selected.
How can I cange this default.Not 100% on your needs but you could create a view off the dimension and use
the view in your cube as a dimension that has the criteria you need.
Ray Higdon MCSE, MCDBA, CCNA
--
"Franz Chernjak" <f.ch@.gmx.at> wrote in message
news:OuwbWzF%23DHA.3428@.tk2msftngp13.phx.gbl...
> If I paste a dimension in excel (import data) per default all data is
> selected.
> How can I cange this default.
>
>

OLAP

If I paste a dimension in excel (import data) per default all data is
selected.
How can I cange this default.Not 100% on your needs but you could create a view off the dimension and use
the view in your cube as a dimension that has the criteria you need.
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Franz Chernjak" <f.ch@.gmx.at> wrote in message
news:OuwbWzF%23DHA.3428@.tk2msftngp13.phx.gbl...
> If I paste a dimension in excel (import data) per default all data is
> selected.
> How can I cange this default.
>
>