Best Of
Re: Include Calculation Effort metric in Anaplan Classic
That's an amazing feature. Would be very useful, indeed!!
Re: Trigger an action with a boolean
I would also like to see this functionality. My users want to be notified when a review process reaches a certain level (ie when a certain boolean field is marked TRUE). We can give the 1st-step user an Action button to send an email to the 2nd-step users, but that Notification Action requires a separate click and is not automatic.
Re: List of subprocessors
Notification for removal of A2P Technologies LLC (Equinox Agents) from the subprocessor list.
LisaM
Re: ROUND Function Not Always Rounding
Hi - thanks for your feedback. The behaviour you've observed is a result of the way that the TEXT function works, and it depends on the magnitude of the input value, as follows:
- For input values smaller than 1e-3, TEXT will always return a result in scientific format
- For input values between 1e-3 and 1e7, TEXT will return the decimal presentation of the input value
- For input values larger than 1e7, TEXT will return a decimal presentation for integer inputs, and output in scientific format for non-integer input.
So at present, the only way to guarantee that you'll see a decimal representation (rather than the scientific format) for large input values is to ensure that they're rounded to the nearest integer.
Re: How I Built It: Flagging hierarchy list levels
Thanks for this informative tutorial. It is similar to an earlier post which uses the same concept of grouping.
Thanks @damien.bouquier and @TimPeterson for introducing this new concept to us.
Re: Increase end user adoption with smart filters
Really glad this article is mentioned in the L3 certification. Content here is a perfect addition to the lesson. Thank you!
Re: Anaplan Mobile App Version
I think there are a lot of things that are missing too - Anyone can confirm this?
like freezing the first column when scrolling, the only function of mobile app version of it is just that it turns everything vertical…..
GAPER
Custom waterfall methodology
Author: Anya Skvortsova is a Certified Master Anaplanner and CoE Lead at Asana.
Purpose: There is more than one way to tackle the waterfall calculations. I’d like to share one custom variety that proved to be especially handy for use cases of new asset depreciation and revenue recognition. Customers seems to like the characteristic “waterfall” shape that this approach can provide and visibility into each period’s data/cohort composition.
UX setup: It starts with a user-friendly input layout. The screenshot below illustrates New Asset Spend grid where the user can input dollars spent by month, type of asset, company and department. I will use depreciation example below; revenue would follow nearly identical setup (say, input/upload revenue by channel, line of business, contract terms etc.).
The next module contains user inputs for depreciation term.
Backend mechanics: For each asset we want to know how much to depreciate a month and for how long. This custom waterfall setup takes 3 modules.
Step 1: We calculate the straight-line depreciation as Spend / Term. This is just an additional line item in the input module.
Step 2: Then we need to define for Anaplan the period when to start depreciating.
This is accomplished with the help of custom time module and respective mapping to the regular timescale periods.
The formula in “Custom Month” line item populates the relative number of forecast period in which the spend has occurred.
The time map uses PREVIOUS () + 1 to produce forecast month number and align it with the custom period dimension using FINDITEM.
Step 3: Bring it together into waterfall shape. Match the 1st depreciation period from input module to 1st custom period in calculation module and set the condition to stop. We are aiming the view below.
First line item in this module produces the Boolean checkmark when 1st forecast period of timescale matches the 1st custom period.
Life counter keeps track of how many periods has it been.
‘Depr Amnt’ is only calculated if the count of periods does not exceed useful life term.
The blueprints are attached below. You can take the model to the next level by advancing to the Balance Sheet and calculating capitalized spend and accumulated depreciation.
Please feel free to leave a comment with questions!
AnyaS
Re: Use of PREVIOUS function
And, if you are only looking at the year, change the timescale for Previous Volume to Year instead of Month.
