TM1 Forum

Hi guys,
we have commented out SKIPCHECK on one of our cubes. I know this is not the best approach but as we are unable to use feeders and we need to calculate ConsolidatedAvg values on hierarchy nodes we can't use feeders at all.

Is it possible that this is causing "Unable to load cube" in TM1 apps? The security is configured correctly and users are able to work with the cube. But sometimes they are getting "Unable to load cube" error and the view disappears from the application. When they log out, close the browser, log in again and open the application the view is working correctly.

Additionally, we are getting #N/A, circular references and stack overflow errors in the log file. But when I change the view (ie. pivot dimensions) the values are calculated. Measures affected are used for calculating BOP/EOP values.

I'm a bit confused by this behavior so any clarification is much appreciated!

BR
Vladino

I think what TM1 is trying to tell you is that you have some problems with your rules. Stack overflow is from too many dependencies in the rules. What I mean is Z is dependent on Y, which is dependent on X, which is dependent on W,.....and so forth. It could be that taking off SKIPCHECK exposed this. It looks like that's exactly what you have with the EOP to BOP linkage. When you are doing BOP to EOP linkage it can't be at the exact same dimension elements for all the other dimension in the cube. That would result in a circular reference. You have to break that linkage on at least one other dimension. Also, make sure you don't have any intersections where A is part of the calculation for B which is part of the calculation for C which is part of the calculation for A. Both of these errors are really easy to do when you have time period linkage like you do. NA means you have another math error, usually division by zero using the "/", instead of "\".