Phil Parkin wrote:
OK, are these date ranges included in your cube? If so, why are you doing that, rather than allowing the end user to perform the aggregation in a pivot table (or however they are consuming the data)? I mean, why not simply have (Date, DiscountMeasure)?
because the user cant deal with the folloewing example:
If the user requests any date that is between Datefrom and DateTill the 30% discount is relevant, but only appears if the specific dates DateFrom or DateTill are selected. I am intrested if there was a better way to allow the user to show the discount in the date range without creating a single row for every date between the range.
I just tested what the multiplying version looks like. OOOF
I have 1.6 million data rows (already filtered) which leads to almost 500 million Cube rows for a single year.
Sucks i cant simply write them only on the first of the month since the data range can change mid month.
I want to be the very best
Like no one ever was