-
Open source module link in NUX
Suggest to add the "Open Source module" ability to the NUX, incl. the current analysis options available in the old UX. Right now our users can use the open source module function in the old UX whenever they want to dig into the details, see all the underlying formulas/comments, and do ad hoc analysis. Especially, the compare function is quite important as this enables them to quickly do e.g. ad hoc comparison of cycle on cycle development without needing a dedicated comparison table/graph in the dashboard.
Comparison tables/graphs can of course be built in the dashboard, but some analyses are only needed on ad hoc basis. At the same time, having this ability as an end user also provides an interim solution until the model builder is ready to add a standard analysis element to the dashboard.
-
getting the error: "Dimension of mapping used for lookup doesn't match any dimension of the result"
I am doing level 1 model building(Activity-9.2.5 Activity: Add Formulas to Price Growth Rates Staging Module)
When i try to enter the formula for the lineitem 'Unit Price %' i get the following error- "Dimension of mapping used for lookup doesn't match any dimension of the result" .
My Formula- 'REV04 Price Growth Rates'.Unit Price %[LOOKUP: 'SYS04 Location Details'.Country, LOOKUP: 'SYS06 Product Details'.Product Family]
I went to the individual modules from where I am looking up and i can clearly see the respective columns.
-
Drill to Transaction Functionality in the New UX
Drill to Transaction Functionality is considered critical for some partners/clients as it's functionality that has no alternate solution. I have heard specifically from FP&A implementations regarding allocations, as well as ICM use cases, but would love anyone giving kudos to leave comments with additional examples of it's use.
Creating this idea because the standard way of submitting feedback via the New UX is only relevant to those actively using the New UX.
-
February 2026 platform releases and what’s next
Check out the latest Anaplan feature updates and enhancements in our February 2026 official release notes. There you'll find information on:
* User Experience* Board Insights Panel
* Management Reporting on mobile
* Custom action buttons on mobile
* Modeling experience* Four digit calendar
* Forecaster* Holiday calendars
* UX pages trigger
* AWS data residency expansion
* Anaplan XL (version 2602)* General Enhancements* Refresh connections and prompt for username
* Streamlined Favorites menu
* XL3SubmitWriteback function
* Freeform reports* Native Excel formulas
* Control the freeform refresh in the member selector
* Performance improvements* Greater flexibility when refreshing connections
* Overwrite pending writes
* Anaplan data source
What's next?
Please note: The information here is subject to change right up to release go-live time. This post is not a commitment to provide any features by a certain time frame and enhancements to the product may change before release.
Anaplan Data Orchestrator (ADO)
* Dataspace support for ADO UX action buttons
Page Builders will be able to choose a dataspace when selecting Data Orchestrator actions for UX pages, making it possible to locate and add the appropriate actions during page configuration from all dataspaces and not just the default dataspace.
* Match on Name or Code for model links
When Data Orchestrator updates a standard list or a composite hierarchy that includes standard lists it will soon be possible to match on code as well as name. Numbered lists match on code.
* Export Code or Name for module based Data Syncs
When extracting data from a module in a model into Data Orchestrator which includes line items of type list, it will be possible to choose to output the code or name when these are standard lists. Numbered lists will output code.
* Support ADO to Snowflake writeback
Pipelines in Anaplan Data Orchestrator enable automated data movement between Anaplan and external systems. With the Snowflake writeback capability, users will be able to write datasets & transformation views from Anaplan Data Orchestrator directly to tables in Snowflake.
* Support ADO to S3 writeback
With the S3 writeback capability, users will soon be able to write datasets and transformation views from Anaplan Data Orchestrator directly to S3.
AI
* Advanced Explainability
Being able to explain predictions with mathematic precision and at the data point level (SHAP).
* Bulk delete
Allowing users to delete multiple Forecaster objects in bulk and with its dependencies.
* Backtest results write to Anaplan will be optional
Improving run times and data writing size to Anaplan by allowing users to choose if they are interested in sending the backtest results to Anaplan
* Add Forecaster actions to UX pages
For end users to trigger as part of their wider planning experiences.
Optimizer
* Integration with Workflow and Optimizer
Users will be able to run Optimizer actions directly from workflows.
* Use current solution option
When you already have a strong candidate solution, you can use it to speed up the optimization process. This can significantly accelerate the overall solving time.
Enterprise experience
* Hierarchy Chart (Data driven hierarchies with Drag and Drop)
This update will allow users to drag and drop nodes on the hierarchy chart to update hierarchies and see the impact. This enables visual Org modeling and Account Hierarchy Management. We will soon also support a new data structure to build the hierarchy using a data list. Select a flat data list for your hierarchy and select a line item to define the parent. Using a data list offers greater flexibility to visualize and interact with multiple alternative hierarchy structures across dimensions within the Hierarchy Chart. Enabling greater what if analysis capabilities.
* End user re-order
End user will be able to manually re-order rows and columns in a grid via a right hand panel. Enabling easy access to configure the ordering of a Grid
* Combined Grids re-order
Page builders will be able to Re-order the Grid sections as needed in View Designer.
* Module-driven navigation actions
Define dynamic links for navigation action buttons on UX pages by connecting them to URL formatted line items.
* Commenting configurability
Page builders will be able to switch commenting, or just the comments summary, on or off at a page-level giving greater control over how users collaborate on specific pages and the level of commentary they can view.
* Forms accessibility enhancements
Improvements to accessibility and usability when users add new list items using UX forms.
Workflow
* Approve/reject links in emails
Support faster and more direct approval cycles with approve and reject buttons embedded within the emails sent to approvers. Configurable and editable by Workflow Owners this will provide even more flexibility when planning how to engage with planning stakeholders.
* Pause and resume workflow schedules
Providing greater control for users managing the execution of business processes, and ADO sequences, with functionality to temporarily pause scheduled workflow schedules.
Enterprise Security
* CAPTCHA on Basic Authentication
To increase account security, we will soon enable CAPTCHA for Basic Authentication. This feature is designed to block malicious, automated login attempts. No action is required as the validation will be automatic.
If you missed it…
* January 2026: Official release notes and supplemental blog and what’s next
* December 2025 release notes
* November 2025: Official release notes and supplemental notes and what's next
-
Module Information Visibility Restricted for Non‑Admin Users on Anaplan page
Why are non‑admin users unable to view Module information on the Anaplan page, while workspace administrators can? (After click the three dots on the grids right up corner)
Are there any configuration options that allow non‑admin users to view module details without granting full workspace administrator access?
-
Combined Grids: examples in accounting and construction
Author: Jonathan Cushing is a Certified Master Anaplanner and Senior Consultant at Vuealta Consulting.
As a Chartered Accountant and someone who has experience in both in-house consulting roles for housebuilding and construction companies, I was excited by the release of Combined Grids in Anaplan.
For years, when end-users have shown me spreadsheets they wanted to replicate, I've had to explain that a direct replication wasn't possible, or that they'd have to settle for two separate grids with synchronized scrolling, a compromise. Combined Grids resolves this user experience challenge.
Below are two examples of where Combined Grids would improve the user experience from projects I’ve worked on in recent years.
Trial balance analysis
Any Financial Planning and Analysis Model generally involves loading a trial balance from an ERP system to Anaplan and mapping the general ledger codes to a line-item subset that creates the financial statements for historic periods. The below example combines the mappings and error checks into one grid. An end-user can then use the grid filters to look for any missing mappings across the year. This gives end-users greater control and autonomy. They can now use simple grid filters to:
* Instantly identify any missing GL mappings across the year.
* See which GL codes comprise their revenue, providing instant transparency.
By providing this single-source report, we empower end-users and save model builders time that would otherwise be spent creating bespoke filters.
Operational reporting for housebuilding and construction
Another example of a report that I’ve been asked to build on numerous occasions for construction or housebuilding companies is shown below. Users want to see the details of a building site or contract next to a KPI displayed over time. Housebuilders regularly report “by category”, so for example they want to forecast plot sales for secured land in FY27.
The view below gives an analyst a way of seeing this a validating that the data provided by the regional teams is correct. Again, simple end user filters can be applied to the grid on which ever site detail is being reported.
This could be further enhanced by applying conditional formatting based on the site status. This creates a visual Gantt-chart-like view, colored by security status, giving management a clear picture of future revenue stability.
Streamlined Excel exports
Let’s face it, many end users export Anaplan reports to excel. Having worked in FP&A teams and alongside analysts, I’ve often been asked to build an export that shows a contract with details of where it sits within the geographical hierarchy and certain other site information alongside their financials by month.
There are work arounds using labels on exports but generally it results in a lookup formula in excel. Combine Grids gives much better excel reports and the below example is like how the housebuilder I used to work for reported. Building well laid out Combined Grid reports will save end users a lot of effort in excel and will reduce the chance of excel errors in their reports.
Conclusion
It’s clear that combined grids will enhance the user experience, but it further re-enforces the need for a front to back model design approach and following the Anaplan way. Data and lists need to be structured so that modules can be combined, and consistent filters applied to modules.
Questions? Leave a comment!
-
Subset Update on Selective Access Enabled list - Workaround Suggestions?
Hi All,
I'm Currently Optimising some of our Cell-Count Intensive Reporting Modules, I've an almost working solution except for this limitation I'm facing.
We've around 5-6 Reporting modules in our model which is Dimensioned by Levels of Promo Hierarchy X Users, promo Customer Hierarchy X users. Since the promo customer and promo product list grows in size with every promo raised, and mind it we could have mulitple products, customers selection for a single promo. This against Users (~183 Users) blows the model size up and the rate of growth is also noticeable.
The solution is moving from a full Users list to a custom User list subset. Which updates the subset dynamically based on a Boolean tick to enable subset on the UX.
The reason to use the custom user list subset and not the native user subset is because of the manual maintenance required by WSA on the subset. This way data is displayed only for active users using these dashboards at a given time. These dashboards are not daily used so this approach works.
We already have a selective access enabled custom user list which we use for audit, so I leveraged the same list and created a subset which is updated dynamically based on the selection in the UX.
In the custom user list, Selective write access is enabled for the users to only the list item corresponding to their email/Native user list. This way the users see only the data specific to their filter selections in the UX (I map the filter selections from the native user list to the custom list). So it works exactly like the native user list but dynamically only for the users who are using the UX at that time.
However, when a Non WSA user runs the subset update from UX, the action is failing. I learnt this is not permitted.
One way I can think of is to run the subset update from our integration service account. But this needs to happen instantly and not scheduled. Allowing API calls from the UX can be specifically helpful for cases like this.
Any Suggestions and work arounds to tackle this scenario?
Thanks in Advance
-
New UX : Source model selector unsable from page to page
Hi
Sorry for the repost if somebody already realized this issue.
A client implemented to new ALM feature for the standard UX.
She realized that the selector can randomely switch form one source to the other while switching the page.
Of course it's very dangerous. She is performing some UAT on the DEV and suddently she realize that she erased data on the production environnement.
Is it the intented behaviour ?
-
Ability for Board or Worksheet to listen to multiple workspace models
This gives ability for users to look at data sets coming from different workspace models on the same page.
For e.g. financials from multiple subsidiaries of a company (being different workspace models) could be viewed by Corp of the parent company on one single page in an app.
-
Reorder line items functionality for end users
Ability for the front-end users to reorder the line items in a grid in worksheet view. Currently the functionality is availability for model builders only.