TM1 Forum

Hi,
I'm using TM1RptFIlter for the first time in anger, when I have done ordering on an dynamic report before I've always been able to restrict it to a single dimension and put the relevant MDX in the subset definition.

Working on a dynamic report with multiple row headers (4) and a single column header for a 5d cube. I'm assuming the function is intended to work across multiple row headers (otherwise whats the point?).

I'm finding that I am getting my results back nearly sorted but not quite, any views on what could be going wrong?
Same behaviour in Excel and TM1 Web/ PAW. Using Pafe to build the dynamic report. TM1 2.0.7
Sometimes I get the right order when I don't I get the same out of orderedness for the same query consistently (I think..!)
No sorting on the MDX for other dimensions.
I'm sorting versus a ruled fed numeric measure giving the month number of the string month.

Is this a bug?

TM1RptFilter does the same as the filter function in the Perspectives/Architect cube viewer. It only works if the view has a single dimension on rows.

I don't think you can call it a bug. It's always been like this, even if it sucks.

Hi Lotsaram,
Not convinced that it isn't supposed to work across the whole tuple set.
I did some testing vs SData and get reliable correct sorting irrespective of the number of dims in the row position.
You can see in the above screen shot the whole tuple on a row is sorted independently. If it was just picking one dimension to sort on and fixing the other two dimensions then it would not be able to order as above?

Maybe its been fixed since you guys last reviewed?
Doesn't help much as in the other environment I'm working in it is unreliable...
Will raise a ticket and see where I get.