-
New UX: Filters in Saved View getting overridden by selection made in Context Selector
Observed an interesting anomaly in the New UX.
I have a Time Range for 4 years which I've used as a dimension in Module M. I have displayed this Time Range as a Page Selector and applied a filter to show only 1 year and saved this in a Saved View SV.
Now, when I publish this SV in Classic UX, no matter what year is selected on the published list of Time Range, SV only shows the filtered 1 year.
However, when I publish the same SV to the New UX page, the filter in SV is disregarded. Essentially, when I select any year in the Context Selector, the published SV also changes as per the selected year. However, the filters works fine when the Time Dimension is published in Rows or Columns.
In summary:
Classic UX: Filters take precedence over sync with any dimension
New UX: Filters are overridden when page level sync is enabled
Anybody else faced a similar issue? Appreciate any workaround suggestions?
-
Register for our January 29 platform release webinar!
Anaplan's next quarterly platform release webinar will be held January 29, 2026 at 8 a.m. Pacific Time. During this session, we will explore the latest features so you can optimize your Anaplan experience.
Our expert-led session will equip you with a practical guide and live demonstrations to help you get the most out of new features and innovations. Get your questions answered live during Q&A.
Features to be demo'd:
* 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.
Can't make it? Register for the event and a recording will be sent to all who register. A recap and recording will also be posted on Community.
Register here.
-
Filtering non-numeric line items
Hello,
I have read the below articles on how to filter line items using a Line Item Subset. This currently works great for my use case, except I also need to filter and include non-numeric line items like booleans.
The below article runs into the limitation of only being able to filter numeric line items via Line Item Subset. Has anyone discovered a workaround to this? The use case is I want to also include an override checkbox to be displayed however the LISS filter hides it. The only other method I could think of was converting the Override checkbox to numeric using 1 or 0.
Any ideas would be appreciated. I have already upvoted the ideas exchange post, but seeking additional help if anyone has uncovered a workaround.
Thanks,
Daanish
Articles I have researched already:
https://community.anaplan.com/t5/Anaplan-Platform/How-to-filter-line-items/td-p/7727
https://community.anaplan.com/t5/Anaplan-Platform/Filter-Line-Item-in-Module-view-based-on-another-Line-Item/td-p/30629
https://community.anaplan.com/t5/Idea-Exchange/Allow-for-line-item-subset-to-be-more-than-just-number-formatted/idi-p/34484
-
Line Item Subset Formatting
This post is a bit of getting ideas to work around but also see if people are experiencing similar issues.
I think it would be a good idea if Line Item Subsets could inherit the formatting and time settings from the source modules that they come from.
In the situation where you had a KPI which was a %, a number and a currency value, these could be split into 3 separate line item subsets and presented on the same dashboard. This will take up more space as the data will be coming from 3 separate modules. They will also need to be manually maintained for which lines go into each subset if a new line item is added to the source module.
Similarly for time settings, in a situation where a source module has a balance sheet movement that might have an opening balance, some movements which are summed over time, a closing balance and also an average balance. These would also need to be split into separate modules with similar problems as above.
This becomes a bit of an issue when trying to do version variances without using a native version formula. In a roundabout way, an idea of version subsets may also be a useful solution as the variances are only present in the modules where required and not in any input modules.
-
Multi Selection
I would like to ask for a new functionality within Anaplan that could really ease our work with Anaplan. And that is multi selection. I see two ways how to apply multi selection, both very helpful:
1. Multi selection for context selector. Once the dimension is displayed as "Context/Page Selector", it would be great to have a possibility for multi selection which would automatically summed up the selected items from the hierarchy - thus, we would have a possibility to see the sum of the values in the object per e.g. two countries that do not need to have the same parent.
2. Multi selection for drop down lists. When we display the dimension as row or column and we are using custom filters (using another line item with a format "list" to filter the content in the object), it would be great to have a possibility for the filter to have a multi selection - we could choose more than only one item from the list which would result in showing rows/columns that match more than only one item from the list, e.g. rows matching country A and below them rows matching country B.
3. Improvement of Filter in New UX. Alternative to the point 2 (however much less flexible) is to improve the existing filters in New UX in the following way:
a) we should have a possibility to apply them on more than one table. We often need to add two tables next the each other - one with no time, one with time dimensionality, but both creating one input table. In such case it is not possible to apply one filter to both tables which greatly limits the option to use this built-in filter.
b) it should be possible to edit them directly in the table (as e.g. "Search" works) and not in the right panel
c) often, the whole name of the items in the field "Choose" is not visible - once it is longer and has more parents, we are unable to see the whole name of the items in the drop down. This should be changed.
-
Daily Date Format
Hi,
I have a module with a time range as a dimension.
I've set it with a daily time scale, but Anaplan's way of showing daily dates is for example "1 Jan 37" and I need it to be in numbers because when I export it excel doesn't recognize it as the date format that I've set in Windows (OS) (when a date as two digits it's 2000-onwards), so because it is a text, it doesn't consider that region setting from either excel or windows, and it translates it into 1/1/1937 which is wrong.
I did include a line item to show the date but it's not a solution to my problem, and it actually doesn't align with the way the model or the specific module is set up, as I want the dimension to have MMDDYYYY format (or whatever date format but with YYYY) and do not want an additional line item.
If anyone has a solution to this problem, that'd be really helpful
Thanks
-
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
-
New UX ALM
Do read it please.
New UX ALM - Anaplan Community
Misbah
-
Boolean filters not showing up in Product Replenishment UX Page for L2 Sprint 3
I'm attaching the screenshots of the INV01 module and the Product Replenishment UX page. The boolean time filters are visible and working for the time filter modules in the UX page. But the boolean filters for INV01 modules (like Submit Purchase Order Request?) isn't showing up in the UX page.
Please share your suggestions.
-
Import for Weekly Data
I am trying to import Historical Weekly Data, but am constantly getting error.
Please assist how to import Weekly Data?
I tried several times, I have attached Screenshot.