Time Dimension Summary

Hi Team,

I have noticed that when referencing a module that has Time as a dimension from a module that does not have it as a dimension that the formula will not return the highest node in the Time Dimension

E.g. I have a Module with Employees & a Boolean line item and a Module with Employees & Time (with Summary as Sum) & a Number line item. If I enter a value into any of the Employee/Time intersections it will roll up to the 'All Periods' Time dimension. But if I then reference that employee from the original Module it will not return the All Dimensions value

I'm assuming I need to use SELECT:Time.'All Periods' in these circumstances?

Thanks

Accepted answers

Will12

Hi Mark,

Just adding to what Nathan said – the reason for this is that although All Periods acts in some ways like a top level item, in other ways it acts like an orphan item in the time dimension. You can see this when you open a page selector – if it were a true top level item, you'd see the years rolling into All Periods, but instead you see All Periods as a detached item in the tree.

Thanks

Will

DavidSmith

@MarkTurkenburg

You can also use TIMESUM() to bring the values back and TIMESUM() is effectively the same as SELECT:Time.All Periods

They both perform almost identical aggregation

SELECT on a time-period has no overhead at all...it just points to the relevant block

So in fact, they should have identical performance

If you need to use the calculation more than once you can just SELECT it, rather than repeating the aggregation using TIMESUM so SELECT would be the best option.

However, All Periods obviously adds space to the model, and TIMESUM can be used more flexibly to return ranges of time if needed.

Hopefully that helps add some colour on the differences.

David

All comments

nathan_rudman

Hi,

yes you need to provide that to the formula, it will not default to it automatically.

MarkTurkenburg_*8288

Thanks Nathan

Will12

Hi Mark,

Thanks

Will

MarkTurkenburg_*8288

Great explanation Will - that makes sense as to why it doesn't roll up!

Mark

nathan_rudman

Hey goodpoint, I'm often wondering why it is not auto summing. Let me investigate I'll update you guys.

DavidSmith

@MarkTurkenburg

You can also use TIMESUM() to bring the values back and TIMESUM() is effectively the same as SELECT:Time.All Periods

They both perform almost identical aggregation

SELECT on a time-period has no overhead at all...it just points to the relevant block

So in fact, they should have identical performance

If you need to use the calculation more than once you can just SELECT it, rather than repeating the aggregation using TIMESUM so SELECT would be the best option.

However, All Periods obviously adds space to the model, and TIMESUM can be used more flexibly to return ranges of time if needed.

Hopefully that helps add some colour on the differences.

David

MarkTurkenburg_*8288

Thanks @DavidSmith!

Very helpful

Quick Links

Can you help?

Unanswered questions

Hide the cards under "Models" section once connected
Hi Is there a way to hide the cards under the "Models" section once connected, as I would like the users to see only the links to the apps? Thank you
OData Rest API for
Hi, Does anyone know how to get an outbound OData Rest API, (OAuth2) to establish a connection between SAP and Anaplan. Thanks Khaled
Looking for Anaplan End-Users to take a short survey!
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…