-
Issue with double counting bed types
* We added new bed types to eventually move from the old "All Beds, single, double"
* I inputted the data into the new bed types
* Went to double check flow into other modules and found that they are being double counted even though I blanked the original columns out.
* I am not sure why it is still counting All Beds even if it is blank
* Hopefully it is just a simple fix I missed please advise
I tried switching summary to formula and it fixed the overall total but still showed the 136 in "All Beds*
-
Posting Action/Process Details to UX Pages or Dashboards
Some background info: my tenant has around 30 model builders and over 100+ end users who are not model builders. We employ a hub - spoke model structure and often times the non-model builder end users will need to run actions from the dashboards or UX pages and are unable to see the most recent run details since those are stored within the actions tab which is not visible to users without a model builder license. This often leads to issues in communication about when the last time this process was run, leading to delays due to extra runs when the data is already up to date.
We historically used a 3rd party ETL (Workiva) to handle to actions but were looking to reduce our footprint on the platform and consolidate some processes within Anaplan. Workiva had the ability to create time stamps from rendered text files for end user visibility. We are however moving away from that software, so we lose that functionality that we were semi reliant on.
Currently on different App and Dashboard pages you are able to post the actions/processes and change the colors and links. You are unable to post any of the subsequent details about the actions to the pages (Start time, most recent duration, ect.) These details are only visible to Model Builders since general licenses do not have access to the actions tab or model management.
My idea is to build the connection to post those process/action details (start time, duration, and an end time column which populate on action/process completion) to the UX pages and dashboards for increased visibility to end users who are not model builders, which is a larger portion of our tenant and likely the case for many others. These details are already created in the model and likely would not be a large change just creating a Boolean on the action settings to include them or not.
Attached are some locations where they could add the option to show process/action details on both dashboards and the new UX apps.
If anyone has additional ideas on how to post those details though Anaplan, any help or suggestions would be greatly appreciated.
-
Additional Insight Card Open Link not working in Dashboard
Cannot click on the title to open the Card, but in a normal worksheet, I can click on the title to open the card in the bottom window.
In Dashboard, additional insight user has to click on the box icon on the left of the title, which is different from a normal worksheet. Please standardize the user experience if possible.
-
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
-
Context Selector Expand and Collapse: Set Children Default: Opened or Closed
Background:
The first click of a context selector on a NUX board the entire hierarchy opens out all levels right down to the lowest level.
This means the user (all users, but focused on business/end users, executive-level) has to manually collapse each level they are not interested in seeing to navigate to the area they are interested in. With deep product/geography hierarchies this can become very cumbersome.
It impacts my users every time they login into Anaplan.
Solution
I think the best option would be to have a Page Selector Setting where you could set whether children levels are "all opened" or "all closed" - when it is "closed", it behaves like the the Classic UX experience behaved, opening out sequentially level by level depending on user navigation.
After thought
Additionally, my expand / collapse options should persist through my session - right now, if I expand and collapse, then choose a product, and go to choose another product, my expand/collapse I previously did disappears.
The images below are my ideal experience on my hierarchy.
-
Show Line Item Format in New Model Building Experience
The new model building experience is far better than the classic and needing to click into every module if syntax is unknown. A big incremental enhancement would be to add some sort of icon or naming to show you the Line Item type. Adding this naming would allow the builder to better understand what they are referencing and could lead to many less model toasts. In my example attached, it would be great to know if that line item is a boolean, number, etc. so that I can efficiently build.
-
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!
-
New UX Idea - Apply one more model source to all pages of the app at once
One of our model a dev and multiple prod models linked to a single dev via ALM.
We have developed New UX App based on dev with a lot of pages in it.
My aim now is to apply all prod models we have to this app, but the existing procedure is not effective for this idea.
I want to have ability to add new source to the excising app globally without need to select each page one by one.
Per each page i will have to click at least 8 times which is too big waste of time.
-
Training & certification for non-model builder
Hi,
I would like to ask the training and certification available for non-model builders. I would like to learn about Anaplan from user end trouble shoot purpose and guide on UAT, deployment and Dashboard creation but not directly involved in model building.
-
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.