TM1 Forum

Dear all,

I do not want to give up on this before having asked you... I have a rather huge accounts dimension as row headers to drill into, so I will have to work with zero suppression to keep the report readable, but my customer (and I) would very much prefer if the top level lines remained visible even if there are just zeroes in them.

I tried a few things with an attribute to the accounts dimension indicating which nodes to display in any case, but the challenge is feeders of course. Any idea how to solve this?

Thank you
Holger

Put 0.0000000000000001 into the cell.

But - are these active forms? You can insert some lines above the TM1RPTROW formula that are static DBRs to make them persistent.

Thank you Christopher. I thought about that as well, but that would mean some 35 static lines plus a mess of active forms between them... I would not want to make my client maintain that by themselves. And thank you for the 0.0000000000001 suggestion; this would work for N elements, but not for C elements which we are aiming at.

I believe I will give them a check box to switch zero supperession on and off so they can toggle themseleves depending on what they are currently viewing.

Cheers
Holger

As Christopher has stated using DBRs would work if its an active form but you should probably then make sure that the TM1RPTROW function looks at something different so that you don't pick up the static rows twice.

Another option would be to add an extra measure X

With associated rule:

['X']=N:

IF(Account = Static ,1, Y);

Y being the actual measure... then if in an active form you can hide this column... in a cube view it would have to be visible for the zero suppression to work but you would just ignore it.



EDIT FOR CLARIFICATION:

"Static" would be based on your attribute (assuming its a numeric attribute with 1 for static and 0 for all others) e.g. IF(ATTRN('Accounts',!Accounts,'Static')=1,1,Y)

Since I have just realised that you want to do this at C level you would need to do a standard = instead of =N:

and as for feeders you could feed from the ElementAttributes cube... I can't recall ever using one for a feeder though so I am not 100% whether it is possible or not, I assume it is as I have used rules in ElementAttributes cubes before.

HTH

Now this makes really much sense! I may not have time to try that before next week, but I will let you know what becomes of it.

Thanks a lot
Holger

...just to complete this: In the end I decided to add a string element to the measures dimension and fill it in a TI process: If there is either a figure or the account is marked "always display" (this is an attribute), there is a "1", otherwise not. No rules, no feeders. I then use this measure in the Active Report for zero suppression.