TM1 Forum

Hi Dears,

As we know TM1 shows null and zero values as "0". However when we use UNDEFVALS function in a rule of that cube, it shown be for zero values to 0 and NULL values to BLANK. If I am wrong please correct me.

That is my problem. Although when I use UNDEFVALS func in a rule, null and zero values come as BLANK.

I need a solution, I tried all situation.
Please help!

Regards

To be honest I think you need to explain yourself better, Have you read the "requesting assistance guide"? While I think I get the general idea of what you are asking your English is very confusing. I take you mean Null value for String elements? Please add further detail.

I have a metric which is numeric value. It has values that 0,1,2,NULL.
When I use UNDEFVALS in a rule it shows BLANK,1,2,BLANK.
However I want it shows like 0,1,2,BLANK.

Is it clear now?

Hi, Suggest you post all your rules and brief dimension structure of cube.
If you have it working at one intersection and not another this suggests a problem with the rule and not the function. Maybe a rule order problem?

(I'd be interested in the why you want to do this part too, I've been doing this for a while and never found a use for undef)

Cheers,

Taylan,

Taking a stab in the dark here - Its likely that your zero values are being dropped from the server and becoming NULL as TM1 doesn't save zeros to the cubes definition file.

How you should approach this depends on if this value will drive a rule of any kind. If the missing values (Blank/NULL) are the sole determinant that a calculation should happen (the feeder) then you will need to save it as a value of some sort - even if thats -1, so that TM1 will recognise it as a value.

You could then use an IF statement within your excel report to turn it back into a NULL or even custom element format which formats negatives to "NULL" for that one measure.

Kind Regards,
Ben

When did you apply the UNDEFVALS rule to the cube? Before or after you loaded the values, some of which were zero? You have to put that rule on the cube BEFORE you load any data. That's because in the normal operation of a cube, attempts to load zeroes are ignored (unless there was a value in the intersection to begin with, in which case it just clears it). Actual zeros can only be loaded when you have UNDEFVALS on the cube prior to doing the data load.