-
Level 2 Polaris Sprint 3 Exam Question 7 — all answer options marked incorrect
Hi everyone,
I am taking the Level 2 Model Building (Polaris) – Sprint 3 Exam and need help with Question 7.
Question:
“Using the Distribution Center Summary UX page, in March 2025, which Distribution Centers have Stock Exceptions (All Products)?”
The answer options are:
* San Francisco, Dusseldorf, Melbourne, Marseille, and Edinburgh
* Paris, Tokyo, Auckland, London, and Vancouver
* Madrid, Edinburgh, Vancouver, Rome, and Mexico City
* New York, Toronto, Mexico City, Rio de Janeiro, and Rome
I have attempted each option individually across four exam attempts, but every option was marked incorrect.
Could someone please confirm:
* Is this question intended to be single-select or multi-select?
* What page selectors/filters should be set before checking the result?
* Is there a known issue with this question or with the March 2025 data in the Distribution Center Summary UX page?
I verified that I was checking March 2025 and All Products, but I may be missing a required context selector or model setup step.
Thank you.
-
How to approach a user story?
Author: Devrath Ahuja is a Certified Master Anaplanner with over six years of experience in implementing and delivering global Anaplan solutions.
As someone starting out on their Anaplan journey, sometimes user stories and the build can feel overwhelming. Have you ever looked at a user story and wondered, “Where should I even begin?” Do I create a new module, a new list, a subset, or do I already have everything I need? Don’t worry, every seasoned Anaplanner has gone through the same questions and worries as you at some point.
So how do we overcome this challenge? Well, one of the biggest learnings in my journey came from a piece of advice I got from my senior back then which was:
“Break down the task into multiple smaller sub-tasks.”
Because when you try to build everything all at once there are chances you might end up being confused and not even know where to start.
Let’s take an example of a user story from Anaplan’s L3 certification and try to break it down:
As a Regional Sales Executive, I need to be able to add an annual percentage increase “stretch goal” to the Baseline Financial Forecast to establish the Initial Country Sales Target for each country that I manage.
The percentage increase in each country’s revenue projections should be reflected across all product families and quarters of the fiscal year. For each country that I supervise, I want to be able to see the Baseline Financial Forecast values, calculated Initial Country Sales Targets, and the difference between the two values for each product family and the total of all products.
I’ll know this is complete when I can input an annual percentage increase for a country and see the Initial Country Sales Target that results and the difference between the Baseline Financial Forecast and the Initial Country Sales Target.
How do we break this down? Start by answering these 2 simple questions:
* What is the output required?* Initial Country Sales Target
* Difference between Baseline forecast and Initial Country Sales Target
* What are the inputs?* Annual percentage increase
In case something is unclear at this stage, revisit the user story and seek clarification, since it’s always better and worthwhile to spend some time understanding the requirement than to directly jump into build mode to avoid re-work at later stages.
Once we have the inputs & outputs clearly defined we need to answer the question:
“How are these connected?”
Remember, only think about the process and the business at this stage. Don’t go straight into solution mode!
What usually helps here is to create a process flow diagram. It could be a rough one in your mind or drawn with a pen/paper.
Once you have an answer to the above 3 questions, the flow is clear, and you can now jump into solution mode.
Remember: You do not need to replicate an excel as-is into Anaplan! You will use your understanding of Anaplan and leverage its capabilities and functionalities to provide the best solution to meet the requirements.
Elements to be considered at this stage
* Dimensions involved — Think of lists, subsets, line-item subsets
In this user story, we know the input is required Annually (Time – Year) and by Country and the output is by Quarters (Time – Quarter) and by Product Family and Country.
* Source data
The % increase is on the baseline financial forecast as well as the difference is against the baseline forecast, so that becomes 1 of our data points.
Check if you already have that data somewhere in the model and if not, create a new module to import data into it.
* Build
Start creating input modules, output modules, calculation modules. Add the appropriate dimension with the right level of granularity in each of them and start connecting them.
You may notice a difference in the granularity between inputs and outputs, consider if you want to aggregate the data or disaggregate it and use either native summary or Anaplan formulas accordingly.
Refer to the Planual and Anapedia at this stage to get the most appropriate and optimal formulas for your use case. In some cases, if the user story feels too complex, break individual line items into further 5-6 line items and take it step-by-step. Once you have the output, optimize it where possible.
* Validate
Always test out your build. Put yourself in the shoes of the planner and follow the process flow you made earlier. Compare the output you get with the desired output. Fix any issues you encounter on the way. Compare the output at different level of summaries to ensure the calculation works (Especially useful for calculated metrics. E.g – Selling price).
Last but not the least, if you’re still unclear, ask for help. 😄 From your project team, organization CoE, or the Anaplan community!
Note: The above example considers a simple isolated user story. Building models in real-world scenarios will be much more complex and you would also need to consider connection points (to other models, modules), the UX build (this is what the end user will interact with), Security and access setup (DCA/Selective Access/Roles and access setup) and other things. As you advanceor as an experienced model builder or a solution architect, you should also spend a considerable amount of time on the scalability of the current build. Consider if you can scale this to include different versions/dimensions if required in future. Consider if the current user story has any linkages to some other user story and hence maybe needs to already be built with different considerations in mind than it would if looked at in isolation? And, all of this, will come to you as well in due time.
For now, to summarize:
* Identify the inputs and outputs from the user story
* Create a rough process flow diagram
* Identify the dimensions involved
* Identify or Import the source data
* Build empty modules with the right level of dimensionality
* Get into the world of Anaplan formulas and logics!
Bonus: Common mistakes to avoid while building a user story
* Jumping straight into building modules without understanding user story
* Ignoring subsets
* Ignoring summary settings
* Hardcoding logic instead of using mappings
* Ignoring time ranges where entire model calendar is not required
* Not following naming conventions for modules, lists, imports
* Not making use of the notes column to capture key details about the line item
What tips would you add? Leave a comment!
-
Revision tag naming: How a small change today can save time and hassle later
Author: Riley Rafko is a Certified Master Anaplanner and Principal at Slalom.
The context
Recently, a Center of Excellence (CoE) group that I was working with came upon a common, yet anxiety-inducing, issue: a production issue needed to be fixed urgently but many pending changes in the development model weren’t yet tested nor were they ready for synchronization into production.
There are many posts and discussions that reference the process for promoting a “hotfix”. Since this post isn’t about that topic specifically, I will highlight the concepts rather than the details:
* Isolate and sync only the incremental change to the production environment, that which is required to fix the production error via a model reversion to a previous point in time.
* Revert the model to the pre-hotfix point, thereby restoring the new development.
* Reapply the development fix from step one.
The most time-consuming, and potentially error-prone, portion of this process is matching a revision tag with a history ID. The reason for each is as follows:
* Revision tag: used to synchronize only intended development at each step.
* History ID: used for completion of the restore prompt in Anaplan.
The hotfix process requires matching of these two components due to the nature of working with several iterations of time of the same model.
To set yourself up for time savings later, simply add the history ID into the Title or Description in your existing Revision Tag naming conventions.
Include the history ID in each revision tag. History ID is highlighted in the revision tag title in the screenshot above.
The “cost”
To be set up for this, the model history will have to be accessed every time a revision tag is created. It is recommended to copy the most recent history ID to paste into the revision tag name. It will add a marginal amount of time to the creation of each new revision tag.
The payoff
Currently, the hotfix process can be daunting due to the potential of massive history logs. It can involve extracting and converting data then searching/filtering to find the correct model history before the hotfix process can even begin. Instead, when the history IDs are embedded in the revision tag name, CoE users can complete the restoration without referencing the logs (provided that the histories are recorded properly).
-
Avoiding CSV import errors: Three practical tips for Excel uploads across regions
Author: Ayesha Zoha, Certified Master Anaplanner and Manager at Kearney.
One of the most common issues I have found during end user training or UAT is the difficulty in uploading data from an Excel csv. This usually arises because users need to upload small but detailed datasets from existing systems. Even with multiple integrations, data hubs and connectors set up, we still need the ability to upload smaller data sets through an Excel upload.
The issue comes up when users sitting in various geographical locations have different Excel settings (number formats, decimal formats, thousand formats, column separators etc). Because of these regional differences, CSV import actions must be configured correctly to avoid data loss or incorrect mappings.
Here are my top three tips for smooth, consistent uploads across regions, that architects and model builders can follow:
* Structure of the file: It’s very important that before you create an action, the csv file needs to be in the right structure and format.* Create an Excel file with Column headers and format the Columns if needed (in final format that’s needed).
* Save this as xlsx on a SharePoint or local system. This will be the export template which the users can download/refer for creating their file in the csv format.
* Importing data (based on column separator)* CSV file with comma (,) as column separator (Usually followed in India, UK, USA etc)* Save the above file as csv with comma Delimiter, with data. Check the system settings of your desktop to confirm this. (Refer SS1)
If you want to change the Excel format - Use Control Panel from the Start - Search for region - Additional settings - check the List operator with; or,
* Create an Import action to upload this data into the corresponding module using this file. Anaplan shows the screen below with the headers and column separators matched to the right format. (Refer SS2)
* If the column separator is incorrect (e.g., semicolon instead of comma), all data may appear in one column. This indicates a separator mismatch. (Refer SS3)
* CSV file with semicolon (; ) as column separator (Usually followed in EU)* Save the above file as csv with semicolon delimiter, with data. Check the system settings of your desktop to confirm this. (Refer SS4)
* Create an Import action to upload this data into the corresponding module using this file. Anaplan shows the screen below with the headers and column separators matched to the right format. (Refer SS5)
* If data appears incorrectly mapped, it usually means the separator is set to comma instead of semicolon. (Refer SS6)
* UX and end user training* The above steps help you differentiate when building the imports for various formats. In case of multiple regions using the same data imports, create multiple actions and corresponding processes for the same and publish the multiple processes on the board with appropriate instructions.
* Have a training session for users from various regions to explain how the two processes work and what the implication is.
* The same format changes can be done for the decimal format, and multiple actions can be created
CSV imports may look simple, but regional Excel settings can easily lead to data issues if they’re not handled correctly. By standardizing file structures, configuring imports based on column separators, and creating region-specific actions where needed, model builders can ensure accurate and consistent uploads. Clear user instructions and targeted training complete the picture and help avoid errors at scale.
Questions? Leave a comment!
-
Setting formula summary method on a ragged hierarchy to display on org charts
Authors: Upali Wickramasinghe, Certified Master Anaplanner and Principal Solution Architect at Zooss Consulting in Australia; co-authored by Andrew Petersen, Senior Consultant at Deloitte Australia.
We were presented with a use-case to utilize the Anaplan Hierarchy Charts to display an organizational structure with some key elements displayed in the nodes such as Employee Name, Country, and Department. The nature of this organizational structure is an unbalanced or “ragged hierarchy”, which made the displaying of values tricky because the need to use for Formula Summary Method for the Line Items used. We present a method using TIMESUM that provides a scalable solution for any ragged hierarchy use-case that requires to utilise the Formula Summary Method.
Note: This approach only works with the Anaplan Classic engine and was developed before the Hierarchy Card allowed for Data Lists. However, the methodology we present can be used for any ragged hierarchy use case even if the application is not for org charts.
Approach we took
Consider the following List that has been defined as a single ragged hierarchy. The use of a Numbered List is not possible if the need for a ragged hierarchy is required instead of a Composite Hierarchy.
An associated Properties (PROP) module is defined as:
This information can now be easily defined using a Hierarchy Chart in the Anaplan UX as:
As one can see, the line item with Formula Summary method can be displayed accurately on the UX.
Now, consider the additional properties of the Employees to be defined in a simple flat PROP module as:
We would like to LOOKUP some of these Line Items in the same module used to display the values in the UX. A simple LOOKUP can achieve this as:
However, note that we did not set a Summary Method, because no suitable summary method can be applied when a LOOKUP formula is used. Last Non-Blank or First Non-Blank do not yield accurate information.
Therefore, the output looks like:
When presented in the UX, the information looks like:
This is not the ideal output we want because all elements that are Parents will not show the information needed. Only the leaf elements are able to show the information defined in the module accurately.
We used the following workaround to achieve the desired outcome of being able to set an accurate Formula Summary method.
Step 1: Define a Numbered List to hold the same Employee codes defined earlier. We use a numbered list to take advantage of the System codes (i.e. defined by “#”) that are in a sequential order.
Step 2: Create a corresponding PROP module to link back to the Employee data.
Step 3: Map a date to each of these elements.
Here we utilized a simple SYS module to hold a “Starting Date” as:
Then “Offset” the Numbered Lists System code to derive a corresponding date value as:
Step 4: Define a SYS module that can now associate an Employee to the corresponding Date values. Here we utilize the FIRSTNONBLANK aggregation method as:
Now that we have managed to “lookup” the Employee, the associated other attributes required to be presented can be easily derived.
Step 5: Let’s now update the PROP module used for the UX with the following additional Line Items.
The key here is to associate the Employee to the defined Numbered List and then “lookup” the Date that was mapped to that element in the numbered list. Once we have the associated Date, then we can use TIMESUM, which is applicable on Formula Summary Method to elegantly “lookup” the associated attributes needed.
The end result is the module being able to display all the accurate details at each element of the ragged hierarchy as:
Displayed on the UX is:
This approach we present is scalable to any ragged hierarchy and will also function even when elements of the hierarchy is deleted or updated as the SYS module used to map the Employee details with a Date value will simply be BLANK if an element is not in the original hierarchy.
Note that this approach only works in the Classic Anaplan engine, because in Polaris the LASTNONBLANK or FIRSTNONBLANK aggregation methods are unavailable and the TIMESUM function can only be used on Numeric and Boolean values.
Conclusion
This article presented a scalable solution to set a Formula Summary Method on a ragged hierarchy to accurately display values used in the display of an organizational structure in the Anaplan UX via Hierarchy Charts. Although this use case was to present information in a Hierarchy Chart, the approach can be used for any other use cases that require the use of a ragged hierarchy and line items that are not Numeric or Booleans.
Questions? Leave a comment!
-
Simple but useful UX wins in 2026
Author: Manoj Upadhyay is a Certified Master Anaplanner and Anaplan Lead Consultant at Relanto.
Hello Community!
The true advantage for our end users is frictionless planning. When the UX is intuitive, users spend less time on figuring out the tool and more time driving business value. These enhancements are about creating a space where data feels accessible, navigation feels natural, and the interface actually supports the planner's flow.
Anaplan continues to improve the enhancement to the UX and platform every month. I have picked my top simple but impactful UX enhancements from each of the first five months of 2026.
January: Hierarchy chart pagination
January solved the headache of displaying deep, wide hierarchies. Previously, a hierarchy chart with 30+ child nodes would either crash the visual flow or become unreadable.
With hierarchy chart pagination, page builders can now toggle a setting that limits the initial view to the first few nodes (3) . Users can then "page" through the rest.
Why it’s a win: It keeps your Boards clean and professional while still allowing users to explore the full depth of an organization or product list.
February: The board insights panel
February brought the insights panel, a collapsible, dedicated space on the right side of any board. Before this, we had to waste valuable "above-the-fold" real estate on text cards for
instructions or navigation buttons.
Master tip: Move your 'how to use this page' instructions, additional info, and page navigations buttons into the insights panel. It creates a sleek, focused workspace where the data stays center-stage, but help is always just one click away.
March: Page-level comment toggles and dynamic navigation
March was a double-win for builders who care about workflow.
* Enable/disable comments: You can now turn commenting on or off for specific pages
rather than one by one for each card. This saves page builder time and reduces
frustration.
* Module-driven navigation: You can now link buttons to URL-formatted line items.
This means you can build a "deep dive" button that takes a user to a different page based
on their specific selection in a grid. Most important it can navigate to any URL and not
only inside Anaplan apps.
April: MOVINGSUM on general lists (the non-time rolling total)
The standout update for April was the enhancement to the MOVINGSUM function. Previously, this could only be used with the Time dimension. Now, you can use MOVINGSUM across any general list.
May: Hierarchy chart filtering
Following January’s pagination update, May brought a quick way to user-specific filtering inside hierarchy charts. Users can now instantly search for and isolate specific branches/area without changing the global view for everyone by utilizing user specific filters based on any available line item. It gives planners a fast, personalized view of large structures in seconds.
Monthly release notes
I hope you've already discovered these improvements! Below are the links to the monthly release notes:
Month
Liked feature
Core benefit
Original release
note for the month
January
Hierarchy pagination
Visual clarity for large structures
January 2026 release notes
February
Board insights panel
Dedicated space for guidance and KPI
February 2026 release notes
March
Comment toggles
Smarter governance and “cleaner” reporting
March 2026 release notes
April
MOVINGSUM for lists
Dynamic aggregation beyond the calendar
April 2026 release notes
May
Hierarchy filter
Personalized view
May 2026 release notes
Don't wait for your next major model to rebuild to start using these. Specially, the insights panel and comment toggles are "low-hanging fruit" that you can retro-fit into your existing apps today to improve the user experience immediately.
Which of these simple updates has made your life as a builder easier? Share with me in the comments below!
-
Level 2 Polaris Sprint 3 Exam – Question 1 (Need Help)
Hi everyone,
I'm stuck on the first question of the Level 2 Polaris – Sprint 3 Exam and would appreciate some guidance.
Question:
In the INV01 Inventory Ordering module, which of the following are used to guard the Final Shipment Amount line item? (Select all that apply.)
I've already tried multiple combinations of the available choices across several attempts, but I'm still getting it wrong. I'm not looking for someone to simply give me the answer—I would really appreciate an explanation of the logic behind which options are considered "guards" for the Final Shipment Amount line item.
If anyone can explain why the correct options are correct (and why the others are not), it would really help me understand the concept.
Thanks in advance!
-
Need clarification on DCA and guarding line items in Polaris Sprint 3
Hi everyone,
I'm currently working through Level 2 Model Building (Polaris) – Sprint 3 and I'm having trouble understanding how the Final Shipment Amount line item in the INV01 Inventory Ordering module is protected.
I'm confused about the different mechanisms involved, such as:
* IF THEN ELSE logic
* Dynamic Cell Access (Read/Write Drivers)
* The AD02 Inventory Ordering Overrides write-access Boolean line items
Could someone explain, conceptually, which mechanisms are considered to "guard" a line item and how they differ from one another? I'm trying to understand the design rather than looking for the exam answer.
I've attached the question for context.
Thank you!
.png){kind=icon}
