[Mondrian] RE: Excel 2007 Support

[Sergey Mazin]

Here is response from SSAS.
          <Tuple>
            <Member Hierarchy="[Store]">
              <UName>[Store].[All Stores].[USA].[WA].[Bellingham].[Store
2]</UName>
              <Caption>Store 2</Caption>
              <LName>[Store].[Store Name]</LName>
              <LNum>4</LNum>
              <DisplayInfo>0</DisplayInfo>
              <PARENT_UNIQUE_NAME>[Store].[All
Stores].[USA].[WA].[Bellingham]</PARENT_UNIQUE_NAME>
 
<_x005B_Store_x005D_._x005B_Store_x0020_Name_x005D_._x005B_Store_x0020_Type_
x005D_>Small
Grocery</_x005B_Store_x005D_._x005B_Store_x0020_Name_x005D_._x005B_Store_x00
20_Type_x005D_>
 
<_x005B_Store_x005D_._x005B_Store_x0020_Name_x005D_._x005B_Store_x0020_Manag
er_x005D_>Smith</_x005B_Store_x005D_._x005B_Store_x0020_Name_x005D_._x005B_S
tore_x0020_Manager_x005D_>
 
<_x005B_Store_x005D_._x005B_Store_x0020_Name_x005D_._x005B_Store_x0020_Sqft_
x005D_>28206</_x005B_Store_x005D_._x005B_Store_x0020_Name_x005D_._x005B_Stor
e_x0020_Sqft_x005D_>
            </Member>
          </Tuple>

-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of Julian Hyde
Sent: Monday, January 18, 2010 1:17 PM
To: 'Calum Miller'
Cc: 'Mondrian developer mailing list'
Subject: [Mondrian] RE: Excel 2007 Support

What response does SQL Server Analysis Services produce to the same query?
If it generates a sequence of elements called <Store>, I guess I can live
with that.

But it seems like bad design practice, even in XML, to have child elements
identified only by position, so I'd be surprised if this is intended
behavior. And it's not going to translate well into JSON, since the a member
becomes a JSON 'struct' and it doesn't make sense to have the same field
more than once.

Julian

> -----Original Message-----
> From: Calum Miller [mailto:calum at millersoft.ltd.uk] 
> Sent: Monday, January 18, 2010 3:02 AM
> To: jhyde at pentaho.com
> Cc: 'Mondrian developer mailing list'
> Subject: Re: Excel 2007 Support
> 
> Hi Julian,
> 
> Admittedly, this does look at bit odd but it does work with all the  
> properties lining up in Excel. When I find some more time I will try  
> again with the associated property names, but this approach 
> will work  
> for now.
> 
> Calum
> 
> On 18 Jan 2010, at 10:21, Julian Hyde wrote:
> 
> > Calum,
> >
> > Looks mostly good, but it seems a bit strange that member 
> properties  
> > all
> > have the same name. They're all called 'Store' in your 
> reference log:
> >
> >                                <Tuple>
> >                                    <Member Hierarchy="Store">
> >                                    <UName>[Store].[All
> >                                    Stores].[USA].[WA].[Bellingham]. 
> > [Store
> > 2]</UName>
> >                                    <Caption>Store 2</Caption>
> >                                    <LName>[Store].[Store 
> Name]</LName>
> >                                    <LNum>4</LNum>
> >                                    <DisplayInfo>0</DisplayInfo>
> >                                    <PARENT_UNIQUE_NAME>[Store].[All
> > Stores].[USA].[WA].[Bellingham]</PARENT_UNIQUE_NAME>
> >                                    <Store>Small Grocery</Store>
> >                                    <Store>Smith</Store>
> >                                    <Store>28206</Store>
> >                                    <Store>22271</Store>
> >                                    <Store>3561</Store>
> >                                    <Store>2374</Store>
> >                                    <Store>true</Store>
> >                                    <Store>5203 Catanzaro Way</Store>
> >                                    </Member>
> >                                </Tuple>
> >
> > Please clarify this point and I can check in.
> >
> > I agree that we should only return slicer members that are 
> explicitly
> > mentioned in the WHERE clause. As you know previous 
> behavior was to  
> > return
> > all members, including implicit members, ContentType=Data but not if
> > ContentType=DataOmitDefaultSlicer.
> >
> > I've changed the default behavior to include only explicit 
> members.  
> > This is
> > the behavior for ContentType=Data, SchemaData, or  
> > DataOmitDefaultSlicer. In
> > fact Data and DataOmitDefaultSlicer now have identical behavior.  
> > I've added
> > a new ContentType value, ContentType=DataIncludeDefaultSlicer, if  
> > people
> > want the current behavior, that is, to return all members even  
> > implicit
> > ones.
> >
> > Julian
> >
> >> -----Original Message-----
> >> From: Calum Miller [mailto:calum at millersoft.ltd.uk]
> >> Sent: Sunday, January 17, 2010 1:15 PM
> >> To: jhyde at pentaho.com
> >> Cc: 'Mondrian developer mailing list'
> >> Subject: Excel 2007 Support
> >>
> >> Hi Julian
> >>
> >> I have added a new test to xmlaExcelTest2000.java, called
> >> testExpect07
> >> which checks
> >>  a) Member Properties are in the correct format for Excel 2007
> >>  b) The SlicerAxis is in the correct format for Excel 2007
> >>
> >> The following attached files must be updated to support this test:
> >>
> >>
> >>
> >
> 
> Calum Miller
> Business Intelligence Specialist
> calum at millersoft.ltd.uk
> http://www.millersoft.ltd.uk
> Telephone: +44 (0) 131 208 0202
> Mobile: +44 (0) 7973 249 621
> Skype: calummiller
> 
> 

_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian