-
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!
-
Register for our October 29 platform release webinar!
Anaplan's next quarterly platform release webinar will be held October 29, 2025 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:
* Enhanced planning experience: See features in action that streamline the user experience and improve planning efficiency
* Improved page management: Explore enhancements that make page management faster and easier, including UX page dependency which shows model builders which UX pages are linked to each module
* Polaris functions: Check out functions now available in Polaris, including two Polaris-only functions
* Anaplan Data Orchestrator: See how you can now export inventory pages and datasets to CSV
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.
-
Resolve Workflow Capacity/Performance Issues
We have been excited for the workflow process to be released. Now that it has been released, we were excited to implement it in tandem with a new model that would use the notification feature quite heavily for our approval process and to get a feel for how to best implement it in our existing models.
During the development of the model, where we had loaded the hierarchy, and little else, we enabled the process so that as new dashboards were being added, features where generated, workflow integration would be the final step prior to moving onto the next feature, dashboard, etc. of the model.
After working with workflow enabled for the level of the model that would be needed to idenify users attention, the entire model and workstation became bogged down. Things that were instantanous took 10-20 seconds. Things that would take longer (eg: an incorrect formula) would become expedentially longer as long as several minutes of non-responsiveness. Obviously, we disabled the feature with great disappointment.
We used a relatively large data set of over several hundred thousand list members, and during the testing process wasn't even using the largest list that may have been needed.
-
New UX: Show Description when Title field is empty
Currently, if card has no name, description icon isn't displayed on dashboard. But sometimes we don't want to enter the title, but we need to show the description - and also don't waste the space above the card just for that small icon.
If this is not feasible, at least we should see some kind of warning in the card designer view, that because there is no title, description won't be displayed.
-
Collapse / Expand Hierarchy Functionality in Modules and UX Grids
In current standard grid modules and UX Grids you can't Collapse & Expand hierarchies of Lists/Line Items/Sublist like you can do in Excel (see below). Considering that sometimes hierarchies can be huge or you want to Collapse one part but Expand another - it would be good to have such functionality
-
Export PDF for board
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:
In Board PDF Export (whole page) – Only the visible content is getting exported not the scrolled content.
How often is this impacting your users?
Mostly
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Model Builders, business/end users and executive-level business users.
What would your ideal solution be? How would it add value to your current experience?
Exported PDF file should include all the grids and their scrolled contents that are available in the page.
-
Export Data source
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:
As of now exact source of export data is not shown in source object for the action.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Model Builders
What would your ideal solution be? How would it add value to your current experience?
There should be a tab which should show exact source of the export action(right now it does not show saved view from which export action is created).
-
Line Item filtering
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:
Right we need to create filter with the line item subset to show lines according to dimensions.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Model Builders
What would your ideal solution be? How would it add value to your current experience?
Anaplan should provide functionality to filter line item based on selection or booleans for all formats.
Example - if there are 100 line items in a module and most line items to be shown to all businesses but only handful to be shown to a particular business then you can filter those line items.
-
Export file name basis on date
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:
As of now when we run an export action it will always export file with the name we have created the export action.
How often is this impacting your users?
Everytime
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Business/End Users & Executive-level business users
What would your ideal solution be? How would it add value to your current experience?
When a user when exports data in a file it should be able to give export name basis on date ,month & year.
-
Bulk change source model in app
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:
Option to change models in an App. Currently we have to change for individual page for same model, it should be so that we can change a model for all pages it's applicable on.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Model Builders
What would your ideal solution be? How would it add value to your current experience?
To be able to bulk change source model for pages with same source.This will save model builders time in changing apps source model.