TM1 Forum

I'm not sure if this has come up before. I have a vague feeling it has but if so it wasn't fresh enough in my mind to save a whole lot of unnecessary pain and annoyance due to a bug in the rule compiler in CX 10.1 giving an erroneous error message and refusing to save a rule.

The following string comparrison of a DB() string value to element name reference throws an (incorrect) error of the type "incorrect logical comparison" and won't save the rule. Doesn't make sense, nor should it as an element name must be a string and the DB reference is for a string value.
After much muttering, swearing, abuse of furniture, etc. it turns out that the error in the rule evaluation can be gotten around by reversing the order of the comparison. That is the following works and compiles no problem: Note that if a similar comparison is the 2nd, 3rd etc logical comparison in the IF then the order of comparison doesn't seem to matter. If the comparison is for a string literal or another DB reference then the order doesn't matter, it only crops up it seems for a !dim reference. Plain stupid as an element name can't be anything but a string.

I don't have TM1 10.1 to test against but I assume this bug is probably there too. Anyone else banged their head against this bug before and know if it is fixed in 10.2?

I have dug up this thread on pretty much the same subject. I think Duncan's explanation is bang on.

qml wrote:I have dug up this thread on pretty much the same subject. I think Duncan's explanation is bang on.

I think you're right, so the rule compiler issue is with !dim followed by & operator as it assumes the "&" is still part of the string belonging to the dimension name. Still a bug and a right PITA though!

Have you tried either putting the conditions within Parentheses e.g. or just the dimension reference within Parentheses e.g. I would expect both examples to work fine. The first example can also make the rule easier to understand if there are multiple conditions.

Bert wrote:Have you tried either putting the conditions within Parentheses ?

Good suggestion, parentheses also works to escape and close the !dim reference and avoids the error.