Rules and DataSpread in Cognos Insight

[Froyo]

Hi there,

I have a dimension OE which is a hierachy dimension.

OE1
-----OE2
-----OE3
-----OE4

There is another dimension "Sales targets" and a rule to derive the C-Elements from the OE dimension, but only for some sales targets.
So there is a rule

[...some conditions...] = C: IF(salesTargetType = A,1,IF(salesTargetType = B,2, STET));

SalesTargetType is da DB() Statement. A value from another Cube but doesn´t matter for the problem.

So i would expect, that in case A and B I don´t have the possiblity to type in values in Cognos Insight.
But if the sales target isn't of type A or B, OE1 isn´t derived, so I would expect to have the possibility to type in values on it. But I´m not.

Why?

Best regards

[tomok]

In order for the cell to be open for input it can't have a rule active for the cell. Using STET as the OR condition in your rule doesn't do that. Replace the STET with CONTINUE and you should be able to input into cells where the OR condition is applied (this is assuming you don't have a rule somewhere else that applies to those cells).

[Froyo]

But I tried the same with N-Cells:

[...some conditions...] = N: IF(salesTargetType @= A,1,IF(salesTargetType @= B,2, STET));

And in that case I`m able to put in values in the cell if salesTarget isn´t of type A or B. So the STET command does like I expect for N-Cells but behaves different for C-Cells.
Doesn´t make sense to me.

Anyways CONTINUE has the same behaviour.

[ioscat]

your IF is wrong, isn't it? it is not possible to be compiled.

[Froyo]

There was a Typo (one ")" to much). Its just a short version I posted. The statement I use is working well, but the problem is the handling of C-Elements.

[ioscat]

do u use "@=" instead of "=" ?

[Froyo]

do u use "@=" instead of "=" ?

Yes, I do. Sorry, tried to explain the case as simple as possible, so I wasn´t looking for 100% right syntax

[declanr]

But I tried the same with N-Cells:

[...some conditions...] = N: IF(salesTargetType @= A,1,IF(salesTargetType @= B,2, STET));

And in that case I`m able to put in values in the cell if salesTarget isn´t of type A or B. So the STET command does like I expect for N-Cells but behaves different for C-Cells.
Doesn´t make sense to me.

Anyways CONTINUE has the same behaviour.

You can't enter values directly to a C level cell... (unless it is a string cell)

[ioscat]

right click on cell - edit status.
what does it say?

[Froyo]

You can't enter values directly to a C level cell... (unless it is a string cell)

I can. Cognos Insight has a data-spreading feature for Consolidated-Elements.

right click on cell - edit status. what does it say?

C-Cell with the Rule
[...some conditions...] = C: IF(salesTargetType @= A,1,IF(salesTargetType @= B,2, STET));
Cell is not editable: Cell is Rule-derived

N-Cell with the Rule
[...some conditions...] = N: IF(salesTargetType @= A,1,IF(salesTargetType @= B,2, STET));
Cell is editable

--> Different behaviour of N and C Cells.

C-Cell withouth the Rule
Cell is not editable: Element xxxxx is consolidated (--> Spreading possible in Cognos Insight)

[Froyo]

Another interesting fact:
The data-spread feature of architect is working for the C-Cell...

[ioscat]

Try using rule with STET and rule with CONTINUE and right click - cell edit status

[Froyo]

Try using rule with STET and rule with CONTINUE and right click - cell edit status

Cell is rule-derived in any case.
Seems to me like a bug. I`m able to do the data-spread in Analyst (no matter if I use STET or CONTINUE which in my opinion should do the same for the given case) but not in Cognos Insight. That makes no sense.

[CImax]

In Cognos Insight any cells that are non-edittable are grayed out and does not allow any input. The cell has been incorrectly flagged as a non-edittable. This bug will be fixed in a future version of TM1.
The difference is that Architect lets you try a spread on any cell and reports a failure if it doesn't work. Cognos Insight obeys the cell status and doesn't let you try.