Look at following Query
-- the first query
with
member [Promotion].[Promotion Category].[No Discount und Reseller] as
aggregate({[Promotion].[Promotion Category].&[No Discount], [Promotion].[Promotion Category].&[Reseller]}, Measures.CURRENTMEMBER)
SELECT ADDCALCULATEDMEMBERS([Promotion].[Promotion Category].members)
ON COLUMNS,
CROSSJOIN({[Product].[Category].[All Products],[Product].[Category].[All Products].children},
{[Measures].[Customer Count],[Measures].[Internet Sales Amount]})
ON ROWS
FROM [Adventure Works]
--and the second query
with
member [Promotion].[Promotion Category].[No Discount und Reseller] as
aggregate({[Promotion].[Promotion Category].&[No Discount], [Promotion].[Promotion Category].&[Reseller]}, Measures.CURRENTMEMBER)
SELECT ADDCALCULATEDMEMBERS([Promotion].[Promotion Category].members)
ON COLUMNS,
CROSSJOIN({[Product].[Category].[All Products],[Product].[Category].[All Products].children},
{[Measures].[Customer Count]})
ON ROWS
FROM [Adventure Works]
The first query gets wrong result for the distinct count measure, the second one gets the right result.
I have tested it against build 2184 and buld 2195. Both have the same result.
Is the bug already fixed in SP2?
Yes, the problem was fixed in SP2. A public CTP release is scheduled to come out in a few weeks.|||
It would be more exectly if you wrtie "is scheduled to come out in a few weeks - 1", because you wrote more then a week ago the same words "a public beta release is scheduled to come out in a few weeks."
|||Nothing has changed to the release schedule since last time but unexpected things could happen before the software is actually released. Just don't want to promise you a specific date since it is out of my control, or any individual's control for that matter.
, 
}