TM1 Forum

Hi, I hope someone can offer some advice. We are working with Tm1 9.5.2.

A user is going into a cube and amending dates that effect calculations (driven by rules) in a cube view through Architect. This in real time through rules effects data in other cubes. A TI processes runs off these cubes to consolidate the data on demand. I can see in the transaction logs that the user amended the data at 11am this morning and the consolidation process was run at 1pm, with no error. However some of the data that has recalculated was not consolidated (I cant prove it was calculated at 1pm but can see the user made the amendment at 11am). I have re run the process and it worked without changing any data.

There has been a number of issues like this, and I am wondering if there may be a problem with the way the user is entering the data on their laptop and it submitting to the server to recalculate. Would the transaction log, record an entry even if the user does not recalculate/submit after entry?

Can anyone recommend any solutions or ways to investigate this? At the moment I am considering exporting data to text file every 10 mins from the calculation cube (Theres only 2000 rows and 2 columns required), as I suspect the data was not properly submitted and I would like to know the time the calculations changed.

if rule-calculated values are not consolidating then that indicates a feeder problem. Do you have conditional feeders in the cube(s). Do you have ReEvaluateConditionalFeeders set to TRUE in your config file?

Thankyou for your reply:

I have reviewed the feeders and re-evaluate feeders is set to T in Config. I have found the problem appears to be around using the DAYNO formula. A user types in a date in this format 31/03/2014 as a string then a numeric rule (below) calculates the serial number. Note this is fed from another numeric value which is input when the date is entered:

DAYNO(
SUBST(DB(cube ref....),7,4)
| '-' |
SUBST(DB(cube ref....),),4,2)
| '-' |
SUBST(DB(cube ref....),),1,2)

There are occasions when the users enters a date and the DAYNO calculation is not working or providing a serial number for the rest of the model. I have examined the feeders for this cell and it is very simple that a value which is always entered before a date is entered feeds the DAYNO calculation.

Any ideas?

Feeders only control whether or not a value consolidates up a hierarchy. Leaf-level cells that are rule-driven will always have a value (assuming the calculations work and there is data in the operands), regardless of whether said leaf-level cell has been fed or not. Have tried right-clicking on one of these leaf-level cells and doing a Trace Feeders to see if it is truly being fed? If fed via a string, do you have a FEEDSTRINGS statement in your rules?

tomok wrote:Feeders only control whether or not a value consolidates up a hierarchy.

You're selling feeders a little short there. They also have a knock on effect if the value is used in further calculations and also when you supress zeros they will disappear,

Jim.