If the timescale is set to Months then the formula would be ITEM(TIME), not ITEM(MONTH). Or are you using a fake timescale called MONTH? If so you need to map it to numbers in a module to use operators like <=. You could also explore switchover if you are using Anaplan versions, though the switchover month would be the same for everyone at all times which may not be the case for your current month selector. I agree with @Misbah that screenshots would help here.
... View more
Hi all As @ArunManickam pointed out, a poorly performing model will manifest itself in the UX just as in classic. So if the experience for users is slow when changing data, running actions etc, then optimising the model will definitely improve things. Similarly if you have very long lists as selectors or in a grid, this can degrade performance as the selector renders or the grid scrolls. However, pages do render as you scroll now, as do grids with lots of rows. So the time it takes to render the top of a long page in the browser is less than when the whole page was loaded before seeing it. However this does mean that when you scroll down, it has to render the next view as you go, which obviously takes a little time. I too have had to challenge this "everything on one page" request from some customers. In general, the more cards on a page there are, the longer it takes to render. But on pages without endless scrolling, the differences are marginal. So a design paradigm to focus users on specific areas when they visit a page, and have multiple pages for each part of the process with a well designed navigation, will perform better than trying to shoehorn everything on fewer, longer pages. This is good practice anyway, not least because it enables the page builders to deploy the best page types for each focus area. Hope that helps! Andy
... View more
For a set of measures, end users want to be able to choose any two versions and see the calculated variances between them. They also want to see a visualization in the form of a waterfall chart that explains the difference between the selected versions.
Let’s say we have a summary measure, EBITDA perhaps, that is made up of 10 component items, and that we have 6 native versions in our model. The user wants to be able to choose any two of those versions and see the variances for each component and a chart showing the bridge between the EBITDA of the first version with that of the second:
Native versions in Anaplan provide for simple variance calculations between versions, e.g. Actual – Budget. But it is common to have many versions—Actual, Budget, 11 monthly forecasts per year, Scenarios, etc. Adding calculated versions for variances between these is not a good option for the following reasons:
A lot of needless space would be used in modules where they are not needed.
Usability is compromised in many cases.
High maintenance burden.
Variances are often nuanced calculations too. For example, the signage might be different depending on the display protocol of an item in a P&L list, or whether an increase in a value in a list item is deemed to be favorable or unfavorable.
All of the above means that in most cases, variances are handled better and more easily as line items.
We will have a data module somewhere in our model with the calculated components by time and version (and any other dimensions the module Applies To, such as Cost Centers). Here I have just entered some data manually:
Each component is a line item, as you would expect.
In Anaplan, we can’t have line-item calculations that intersect with one another, so we need to convert the components to lists in order to calculate the versions and the variances as line items. This is necessary to engineer the calculation to be based on end-user version selections.
The first P&L Component list is a Line Item Subset. Mine looks like this:
Now, we need a module to collect the data against this LIS:
At this point, we need to consider the requirement for a user to be able to select any two versions. This feature is best served through the use of list formatted line items so that they can select from dropdown lists:
This is better than offering a Boolean selection because they can only pick one item for each version.
But—it is not possible to format a line item with Native Versions. We need a list that replicates the Versions. A line-item subset will work well here, but we need to model a way to calculate the versions as line items.
Above we have a module by LIS P&L Components and Versions. We need to create LIS Versions, but in Anaplan we can’t dimension a module by more than one Line Item Subset. We, therefore, need a module that uses a normal list for the P&L Components in place of LIS P&L Components. If it does not already exist for other purposes, then the creation/maintenance of this list can be synchronized with LIS P&L Components via a System module.
The new module CAL02: P&L by Component List looks exactly the same:
…but is dimensioned by P&L Components, a normal list, but NOT Versions. This is because the line items represent the versions. You can see the full formula for Forecast 2 in the formula bar above. The formulae for the other line items are identical but for the version names.
You will also see in that formula that I have used a simple Mapping module to map LIS P&L Components to P&L Components, which has a FINDITEM formula to populate it.
I can now build my LIS Versions list to use in my Version Selection module to format for use as a dropdown:
I also need a module dimensioned by LIS Versions to use as a source for my variance calculations. This also needs the P&L Components list since we can’t have two Line Item Subsets in one module:
Again, this looks exactly the same with a simple Collect formula bringing the data through.
Now we are in a position to build our Variance Calculation module, based on user selections:
Now we have our variances calculated depending on the versions we select. All good so far. But the variance column by itself does not provide all we need for the waterfall chart. We need to model a SINGLE COLUMN with the EBITDA of Version 1 as the starting point, the variances for each PL Component between versions as the movements, and the EBITDA for Version 2 as the end point.
To do this we need another module, with the components converted back to line items. I created a Waterfall Report module, without Versions.
You will notice that another Mapping module is used as a lookup here to avoid multiple SELECT statements that go against the Planual. The module uses LIS Waterfall:
…and simple Finditem to populate:
Now we have our start and end values, bookending the movements that bridge between them, in a single column:
This is all we need for our Waterfall chart:
Now, if you think that you will have many users wanting to make different selections while using this feature simultaneously, then you might need to add the Users list to the Version Selection Module, the CAL04: Variance Calculation module, and the OUT05: Waterfall Report module. Take care though, as this might have sizing implications.
... View more
Hi, With respect to forms, what you describe is on the roadmap for Q1 next year. The parent will default to the context set in the page, but still be editable by the user. On a worksheet, in the add multiple items menu, the context of where you land your cursor is respected. Cheers Andy
... View more
Hi @jim_ma Glad you enjoyed the session. The tool which Anne Julie directed to you is now available. It is a useful accelerator and brings classic dashboard components into the UX as custom views, ready for you to augment and develop. It is not, of course, a way to press a button to lift and shift everything. Good luck with it and please report back!
... View more
Intrigued by the UX?
Looking for a practical example of transition from Classic?
In this session, start from your existing Classic Dashboards and learn how to enhance and augment your experience with the UX.
We will focus on enhancing the Classic experience with UX-only features.
Don't forget to explore other assets in Community: The new UX section and it's best practices and training resources are a great starting point!
Watch the video here, download the presentation (.pdf format), and then join the conversation, add comments & questions below!
... View more
Hi. There is a Stat Forecasting Engine app on the App hub (a monthly and a weekly version). There are 30 different forecasting methods built in to the app. I can't see ARIMA specifically, but there are regression and moving average methods. It should be possible to take some of the modelling techniques used for these methods and build out ARIMA. Attached is a file with the included methods listed. Hope that is of interest. I'd be interested to learn more of your use case and follow your journey to solve this. Regards Andy
... View more