Page 1 of 1

Rule Vs Process

Posted: Thu Nov 24, 2011 9:30 am
by plkkw
Hi,

I am new to TM1. I am confused with Rules Vs Process on some feature.
1) "process" can update data in cube, right? Can "rule" store data? or just evaluate data (e.g. query in rdbms, without storing data)?
2) If i run a process to update a cube: "A" (e.g. dimension: month, product) with cells as "1", and then I create a rule in the cube: "A" to update all Jan. data equal to "2" (e.g. ['Jan'] = N:2; ). Then what is the result of Jan figure if I browse the cube "A" (1 or 2)?

Re: Rule Vs Process

Posted: Thu Nov 24, 2011 9:44 am
by qml
plkkw wrote:I am new to TM1.
Welcome. A good place for you to start would be the official product documentation, the FAQ on this forum, and the many interesting thereads on it.
plkkw wrote:1) "process" can update data in cube, right? Can "rule" store data? or just evaluate data (e.g. query in rdbms, without storing data)?
Rule is a real-time calculation that is performed when someone requests data from those cube cells that are affected by that rule. Processes can manipulate the actual values stored in cubes, among many, many other things.
plkkw wrote:2) If i run a process to update a cube: "A" (e.g. dimension: month, product) with cells as "1", and then I create a rule in the cube: "A" to update all Jan. data equal to "2" (e.g. ['Jan'] = N:2; ). Then what is the result of Jan figure if I browse the cube "A" (1 or 2)?
Rules always take precedence over stored values. If there is already a value in the cube when you create a rule, then depending on the version this value will either stay in the cube and be ignored until you delete the rule or will be deleted from the cube altogether (in newer versions). Once you have the rule attached it becomes impossible to input any values into the affected cube area.