-
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.
-
Need Set Global Default Format Grid function in New UX
My users want to make it possible to set Format Grid - Small for all grids in the New UX. This function exists in Classic UX to set all dashboards to Striped, Ruled, etc. We would like to have this opportunity to set all grids of one App in New UX to one style, e.g. Small which will improve screen space utilization.
-
Ability to apply Row and Column header configuration on all grids across a page
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
Currently, each individual grid on a UI/UX page needs to be edited as follows to change the Background color of the row headers and columns.
* Card configuration > Format > Styles > Column headers > Background AND Row headers > Background
This is extremely tedious and time consuming to update across a large page or application when clients require a specific color scheme to be used.
How often is this impacting your users?
This is impacting users in hindering our ability as model builders to quickly create pages that meet accessibility requirements without a significant amount of manual configuring of each and every grid.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
This directly impacts page builders and indirectly impacts everyone else.
What would your ideal solution be? How would it add value to your current experience?
Ideally, page builders should be able to standardize the column and row headers' background color across a page. This could be a starting point as a page setting with the ability to override the background per grid if desired. This would save a ton of time and clicks when updating the colors of an application.
An alternate, less ideal solution would be to provide a checkbox to at least copy over the settings from Column headers to Row headers.
Please include any images to help illustrate your experience.
-
Combined Grids is now live!
Author: Calvin Magondo is the Product Manager, Enterprise Experience at Anaplan.
Combined Grids and multi-module reporting
We are excited to announce the much anticipated enhancement to the Anaplan User Experience (UX): Combined Grids. This powerful new feature and platform capability will address one of the most common challenges for planners and model builders today by allowing you to bring data from multiple modules into a single, unified grid. We’ve already seen customers finding real value in this enhancement from, streamlining UX by reducing unnecessary white space from multiple grids on page, to unlocking more intuitive planning experiences for end users and enabling more efficient model building whilst removing inefficient workarounds.
We developed Combined Grids based on direct feedback from our user community to solve a common challenge: viewing and interacting with related data from different sources in one place. Let's explore what it does and, more importantly, see how early access customers are already using it.
Combined Grids demo
https://play.vidyard.com/jE6fAyopzvibJjUvJ8vyUk
The Challenge: building complex, multi-module views
As Anaplan models grow in sophistication, so do the demands on the UX. Page builders often need to present data from different modules side-by-side. For example, you might want to show product attributes next to monthly sales data, or compare a driver-based forecast with the final plan numbers. While this has always been possible using multiple grid cards, it presented a few common hurdles:
* Synchronizing data: Keeping separate grids aligned when scrolling or filtering required careful setup and could sometimes lead to a disconnected user experience.
* User-driven analysis: Applying a single sort or filter across multiple, separate grids wasn't possible, limiting a user's ability to analyze the data holistically.
* Model building workarounds: To create the ideal view, model builders often had to create "helper" modules or duplicate data, increasing model size and maintenance. This could also mean straying from best-practice modeling principles like DISCO.
* Exporting data: To analyze data from different grids together, users frequently had to export multiple files and combine them manually in an external tool.
Combined Grids was designed to address these challenges directly.
The solution: a single, unified grid with data from multiple modules
At its core, Combined Grids allows a page builder to merge up to five modules into a single grid on a UX page. The key requirement is that the modules share a common row axis. This enhancement unlocks several benefits:
* A unified view of data: All your data is presented in one grid, which saves screen space and provides a more intuitive user experience.
* Powerful end-user interaction: Users can apply a single sort or filter across all the data in the combined grid.
* Simpler model design: It reduces the need for those complex workarounds, allowing for cleaner, more efficient models that adhere more closely to best practices like DISCO. An early access customer said: "Combined grid allows us to avoid creating redundant line items... and more strictly adhere to DISCO and 'create once reference multiple times."
How customers are using Combined Grids
The best way to understand the feature's impact is to see how it's being used in real-world scenarios. Our early access customers have already found creative and powerful ways to put Combined Grids to work.
Streamlining budgeting and reporting at Jaguar Land Rover (JLR)
For their marketing budget, JLR needed to plan values across multiple time periods and for lines with many different attributes.
Before: This required two separate modules — one for the attributes and one for the budget values. On the UX page, users had to input data on two separate grids and perform two separate exports to get a complete picture. Filtering was complex and had to be pre-coded by their model builders.
UX page before Combined Grids:
With Combined Grids: JLR now combine the attributes and budget modules into a single view. Users can input data on one grid and run a single export. Most importantly, users can now apply their own filters and sort by value, giving them far more flexibility for analysis with less upfront work for model builders.
UX page now with Combined Grids:
No back-end filters required, JLR now simply make use of Anaplan’s native filtering for end users.
Creating comprehensive forecasting views at Unilever
Unilever has a large-scale forecasting process with over 800 users globally. Their challenge was to display all material attributes (like Group, Subgroup, Classification) and reference numbers alongside the forecast data in a single view.
Before Combined Grids: This information was spread across multiple grids, making it difficult for users to see the full context at once.
With Combined Grids: Unilever now present all attributes and reference data together in a unified grid. This gives their forecasters a complete and contextual view, helping them make more informed decisions quicker.
Getting started with Combined Grids
Creating a combined grid is straightforward:
* Add a Grid to a page: Add or edit a grid card onto your UX page.
* Select primary module: Choose the grid you want to appear first on your combined grid. Note: The order of modules cannot be changed after creation, so plan accordingly.
* Combine Grids: In "View designer" mode, click on the ‘Add Grid Sections’ button located above the main grid. A right-hand panel will appear allowing you to select up to four additional modules to combine to your primary module. Remember, for grids to be combined, they must have a common row axis so, all dimensions in rows must be present in the additional modules you wish to add.
* Apply customizations and publish: Apply any additional customizations, like conditional formatting or any filters, and when ready, click update and publish the page.
Tip: End users can make use of the existing ‘Freeze rows/columns’ functionality and Freeze the columns in the first module (for example attributes) so they are always visible when looking at your combined grid.
Just the beginning…
We are incredibly proud to deliver Combined Grids, an enhancement that we know many of you have been eagerly anticipating. Our team has worked hard to bring this powerful capability to life, and we see it as just the start of the journey. We are already working on what comes next. In upcoming releases, you can look forward to more flexibility, including the ability to reorder the Grid Sections within your combined grid and better, more clear labelling of Grid Sections when making customizations to your view.
Looking further ahead, we will continue to explore ways to provide even more freedom, investigating how we might allow you to combine more modules, even without a perfectly common axis. We cannot wait to see the transformations, efficiency gains, and time savings you will achieve with this new feature. Your feedback is what drives our innovation, and we look forward to hearing about the incredible solutions you build.
Additional resources
* Combined Grids Webinar with testimonials from JLR and Unilever
* Anapedia documentation on Combined Grids
* Anapedia training on Combined Grids
-
Conditional Formatting on Booleans
As a model Builder I would like to use Booleans as a Basis for Conditional formatting.
For example. I have a Boolean/ Checkbox which indicates that not all fields in a new Item/ setting has been filled. I would like to be able to use that boolean directly instead of reverting to a number.
The advantage would be to save on workspace size,
-
Session Timeout Warning
When the token request is near expiry, the user currently has no awareness of the impending disruptive page refresh. If there were to be a way of sending a notice to the user, preferably on the current page they are operating in, then they would be able to take recommended action to prompt recognition of activity in the application and avoid the refresh. Otherwise, as it is today, users will experience the page refreshing, seemingly at random - as a result of a sort of phantom inactivity.
We are happy to share more examples of this, that our planning community has experienced.
-
Recording now available! January 29 platform release event
If you missed our January 29, 2026 platform release event, the recording is now available!
In this webinar, we highlighted the most recent feature releases and how to take advantage of these in your environment. Our expert-led session demonstrated new features and innovations, provided a technical deep-dive and “how-to”, followed by a question and answer session with the audience.
Topics covered include:
* Modeling in Polaris: Explore how on-demand calculation can positively impact model performance.
* Dimensionality in Polaris: Learn how builders and users can pivot up to eight nested dimensions in a grid view.
* Planning experience: Check out new features that allow page builders to elevate the design of UX pages and present information side-by-side for end users.
* Forecaster: See the latest enhancements to Anaplan Forecaster, a next generation forecasting capability embedded in the Anaplan platform.
Recording
https://play.vidyard.com/YtcWuuHFZVaqM9AapfxRFT
Q&A
* Where is On-demand Calculation (ODC) defined? Anapedia
* Which summary methods are supported with ODC? All summary methods are supported except Formula, Ratio, and None.
* Is data input still supported for combined grids? Yes. Data input is still available for combined grids if you are surfacing leaf levels in the grids.
* Does filtering work on the rows and columns in a combined grid? Yes.
* If 3 grids were added to a combined grid, in what order are they presented? The grids are presented in the order in which they were added to the combined grid.
* Does Anaplan Forecaster only use historical information? Or can you combine inputs in addition to history, i.e., revenue expectations to increase by x%? Forecaster does support external drivers to the forecast. Data collections have to include historical data; related data and attributes are optional. Please see Anapedia for more information.
Note: There may be additional Q&A included in the recording that was answered live.
Catch up on recent releases:
* October* Release notes
* Supplemental blog
* November* Release notes
* Supplemental blog
* December* Release notes
Follow along for future events!
Stay up to date with all platform release announcements by subscribing to the platform release page on the Anaplan Community, and all platform events by subscribing to the events page. Look for the “bell” icon on the page to subscribe.
-
Total positions for nested dimensions
Please add option to change Total positions order on rows/columns when nested dimensions are applied.
Currently it can only be applied towards single dimension. When adding at lease two dimension, order becomes "Before" by default and the following error is returned when trying:
"Cannot group totals on a nested axisSetting totals position on an axis with nested dimensions is not supported."
-
External links as option for clickable Images
I've had a handful of requests to give end users an clickable external link where they can go to submit help desk tickets, contact their company support systems (things like JIRA, Sharepoint sites etc.). What I've found is Image cards only allow for linking other Anaplan App Pages, but not external links. (Please correct me if I'm wrong!)
THE ASK:
Please add the option to designate an external link that will open when a user clicks an image card. (E below)
In searching for what can be done, I've come up with options A, B, C, & D above. But if I'm being honest they all feel like unfortunate workarounds rather than the desired solution. As a guy trying to design the most professional an polished UX experience for each page, I find these options lacking, here's why:
A & B - Grid cards: Can pivot, use conditional formatting; feels big and clunky for such a simple purpose, can't hide the card's backing
C & D - Field cards: Clean and minimal, but so subtle no one really notices it. Field cards do not support conditional formatting; field label does not support use of color, card title does but consumes a lot of vertical space (D), can't hide the card's backing
-
Configurable default selection for context selector
I recently had a question from a client who asked if it was possible to set a default list member (or the top level of a list, eg. all products) as the default for the context selector at the top of a page.
They wanted to be able to select a particular layer, list member or top level of a list and always have it revert back to that level when clicking "Reset" for example.
(I appreciate we could stick the list member at the top of the list but this isn't what they really wanted - they wanted "all products")
Hopefully not a difficult one to add!