Which is more efficient, TIMESUM( ) or [SELECT:Time.All Periods]

If I'm trying to accumulate all time periods from a source module with time dimension to a target module with no time dimension, which option is more efficient? Should I use TIMESUM with no start or end date, or a hard-coded select clause for all periods?

Accepted answers

All comments

MarkWarren

The SELECT will be quicker; the aggregation is pre-done and you are just grabbing that total. The TIMESUM is having to do all that calculation.

rob_marshall

@clarissa

Hope all is well, good to see you one the Community!

As @MarkWarren said, the Select would be better IF the All Time Periods has been checked.

pyrypeura

As note nice thing regarding Timesum is that then you don't need to have All Time Periods in your model.

Quick Links

Can you help?

Unanswered questions

New UX Filtering for Hierarchy sibling
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
A reminder of Bulk Copy - Current year to Prior year version for YoY analysis
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
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.…