Page 1 of 1

Dimension elements wrongly displayed for multiple TM1RPTROW in Active form

Posted: Thu Nov 25, 2021 4:07 am
by wbf
I'm amending an active form to add row dimension (DimC) via TM1RPTROW. There are already two existing TM1RPTROW in the report.

Things I have performed:
1. Remove TM1RPTTITLE for DimC out from TM1RPTVIEW
2. Adding TM1RPTROW before the two existing ones
3. Manually delete all the rows under TM1RPTROW

After rebuilding the worksheet the dimensions in first row underneath TM1RPTROW is correct but dimensions from second row onwards are somehow ordered wrongly.

https://imgur.com/a/QLMC4w7

Funny thing is, I have also rebuild the view in cube viewer and generate via button 'Active form'. The elements ordering in the generated reports are also wrongly displayed (as per url image)

Is there something that I have missed out?

Appreciate for any advice!

Re: Dimension elements wrongly displayed for multiple TM1RPTROW in Active form

Posted: Thu Nov 25, 2021 8:07 am
by Wim Gielis
Welcome to the forum.

Is the version mentioned in your profile correct ? Then please upgrade. IIRC there has been such a bug.

Re: Dimension elements wrongly displayed for multiple TM1RPTROW in Active form

Posted: Mon Nov 29, 2021 11:30 pm
by wbf
That's the version for my personal use only.
This specific client having issue is using the stable version 2.0.9 with Excel 2013 - however, could not find any related fix on 2.0.9.5

Thanks,

Re: Dimension elements wrongly displayed for multiple TM1RPTROW in Active form

Posted: Tue Nov 30, 2021 10:32 am
by Mark RMBC
Hi,

Two questions:

Is the incorrect order being shown in the image the order of the dimensions in the cube?
When you open the active form in TM1Web is the order correct?

If the answer to the above 2 questions is Yes this is the bug I think Wim was referring to.
My understanding is that this had been fixed a while ago!

regards,

Mark

Re: Dimension elements wrongly displayed for multiple TM1RPTROW in Active form

Posted: Wed Dec 01, 2021 4:41 am
by wbf
Thank you both. Will check with support and see if they patch this in any later version