Drill to transaction on module with versions – tip

Hi everyone, I thought I'd share a something useful I recently discovered, which I haven't seen documented anywhere.

According Anapedia, Drilll to Transaction is only supported for formulas like TransactionModule.Amount[SUM:___, SUM:___]

So this means that you can't drill to transaction on a formula like IF ISACTUALVERSION() THEN TransactionModule.Amount[SUM:___, SUM:___] ELSE complicated formula

And that's generally true, but I've found it does work for this specific type of formula: IF ISACTUALVERSION() THEN TransactionModule.Amount[SUM:___, SUM:___] ELSE COLLECT()

I hope some of you find this helpful too!

Will

Accepted answers

All comments

nathan_rudman

Hi Will,

is the collect() part really necessary ?

Will12

Hi Nathan,

The idea is that you can do a complex calculation for your non-actual versions in a separate module. Then you can use a line item subset and the collect() function to pull those amounts into the first module. So you end up with a reporting module that contains actuals and forecast, and allows users to drill to transaction for the actual version.

Thanks

Will

nathan_rudman

you mean if I do a look up in my other module and collect it, the user can drill to transactions on it because of the collect ?

Will12

Hi Nathan,

Not quite – if you have a select in your other module, and then pull it in with a collect like this:

ISACTUALVERSION() THEN TransactionModule.Amount[SUM:___, SUM:___] ELSE COLLECT()

... then users can drill to transaction on any ACTUAL periods, but not on FORECAST periods. The point being, if you tried to use a formula like this:

IF ISACTUALVERSION() THEN TransactionModule.Amount[SUM:___, SUM:___] ELSE complicated formula involving SELECT

... then users would not be able to drill to transaction on any period at all.

Thanks

Will

nathan_rudman

ok I get it. Interesting. will look further into it, if it is intended or not.

Quick Links

Can you help?

Unanswered questions

Can Please explain the difference between a general list,a module,and action in Anaplan.
Can please explain why we create a general list ,a module,and Action ,and what purpose each one serves.🙂
Predefaulting A Feild in ANAPLAN
Hello Anaplan Community, I have a special requirement from a customer and would appreciate your input. Let me explain the situation: We have a hierarchy with three levels: Level 1, Level 2, and Level 3. Screen 1: Creation of Level 1 Items On this screen, the user selects a team. Based on their selection, an action runs to…
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.…