TM1 Forum

Hi All,
When I run a TI process which is loading data into a cube, it is showing a error 'Rule applies to cell' for some particular combinations in cube. But when I check the cube, no rule has been applied to those cells and also the data is loading in those particular cells.
Can anyone please advise how to deal with this error?

Regards,
Rama

I would start by posting it in the right subforum, as it's not an Enhancement idea/request.

As to your issue, it seems very unlikely to me that you are getting the 'Rule applies to cell' message and yet data is still successfully written to the exact same cells. It is more likely that you think these are the same cells, but they are in fact not. The exact error messages combined with a screenshot of what you believe are the cells where the data is being written to would help pinpoint the exact problem.

How are you checking if a rule applies to cells?
What is the data source for your TI (there was apparently a defect with excluding rule-calculated values from source views)?
The best way to ensure you are only trying to write to editable cells is to wrap your CellPutNs in CellIsUpdateable checks.

The most common reason for this is as qml states, but I have an open PMR with IBM on this occuring on cells which I know are not rule targets. Further, it doesn't happen every time, i.e. repeated runs of the process may or may not generate the error, and even the affected cells change. Unfortunately, this second part makes it very difficult to diagnose as I can't construct a good testcase for support.

Hi qml and mattgoff,
Thanks for your valuable replies.The cells are editable(no rule).
I restarted the service and tried, but receiving the same error. Not sure if its a system related issue.

RMishra wrote:Thanks for your valuable replies.

I wish I could say the same. Unless you actually make an effort to provide the additional information that is being asked of you the chances of anyone here being able to tell you with any confidence if it's an issue with the product, or with your solution, or with your perception, are in my opinion very slim.

Hi qml,

Apologies as I was unable to explain it.

I investigated again and found that we have got 2 similar descriptions for two elements in one dimension.
One of the two dimensions is rule calculated and the other is not.
I am receiving the error 'rule applies to cell' in the combination for the element where the rule is not applied as both have the same description.
Now we need to provide unique descriptions to the elements to avoid this error.
Please let me know if it is not clear.

Thanks

We can't really help you with the info you've provided. Please read the Request for Assistance Guidelines. To provide any meaningful help, we'll need cube/dim structure and copy of the exact code that's giving you the error. Screenshots of the cubeview showing the cell writeable would help us confirm you're checking it correctly.

While it's possible you're running in to the same bug as me, it's more likely something else is going on.

Matt

RMishra,

I agree with the posts above, please provide more information.

Are you for instance using an alias that is rules-calculated ?

Hi,

The current scenario is,
We are having an element X.The 2nd element is Y.
The element Y has a text attribute which refers to X.
X is rule calculated. For Y we are loading from TI process and referring to text attribute of Y i.e X.
So we are receiving rule applies to cell error as one X is an element and the other X is a text attribute of Y.

Sorry for the inconvenience. From next post onward I will follow the guidelines.

Thanks again.

In your TI process, you can refer to element Y to get the X (stored as a text attribute).
You could then do (for example) a CellGetN to retrieve the value on X.

- But do you write element X (clearly yoiu say it's rules-calculated so you shouldn't be surprised then).
- What is the rule of X ?

RMishra wrote: We are having an element X.The 2nd element is Y.
The element Y has a text attribute which refers to X.
X is rule calculated. For Y we are loading from TI process and referring to text attribute of Y i.e X.
So we are receiving rule applies to cell error as one X is an element and the other X is a text attribute of Y.

Sorry for the inconvenience. From next post onward I will follow the guidelines.

There's nothing to actually stop you following them now, especially #5:

5) For Rules and TurboIntegrator processes, posting the actual code and the real names of and structures of your cubes, dimensions and elements will be a thousand times more useful than an attempted description of them. You don't need to post real data, but the real code is needed. Pseudo code is obviously not "the real code". When you post something like "Suppose I have cube A and Cube B, and my rule is ['value'] = N:DB('CubeA', 'dim1, dim2'" etc, then three things happen. One, you reduce the chance that a syntax or typing error will be spotted, which means wasting time bouncing posts back and forth to try to get to the root of the problem. Two, you are usually describing what you think is happening, which may not be what is happening. Three, some more experienced members won't even look at the question because they've had too much time wasted by the first two issues in the past.

I have no idea at all what "element X" and "element Y" are in your description above. No idea which dimensions they are in. No idea of whether those dimensions are in the same cube. No idea what the exact description of the error in the error log is, including the (real) element names. No idea what your data source is, No idea what your code is doing with that data, because you haven't posted the actual code.

You will (unless hitting the bug that Matt describes which I doubt is very common or more people would have raised it), get this set of error in one set of circumstances; you have a cellput function which is writing to a combination which is rule calculated. And when you checked it and found that it isn't... you were in fact looking in a different place to where the code is actually trying to write to.

Even a copy of one line of the error log and a screenshot of the view you checked to see whether it was with or without rules would be useful. (Nobody needs to see the actual numbers, just the elements.)

But the description above is not.

You're probably wasting your keyboard, Alan. I asked RMishra for this in my first post:

qml wrote:The exact error messages combined with a screenshot of what you believe are the cells where the data is being written to would help pinpoint the exact problem.

Since that the OP wrote three whole posts without even attempting to provide the requested information.
Four people have tried and failed. Let's face it, not everyone can be helped.