Best Of
new module experience
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:
It is not possible to export the modules view from the new modules experience.
It is possible, but fiddly, to highlight and copy, however you do not get all columns pasted the number of columns can vary
How often is this impacting your users?
Any time they use the New Modules Experience
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
All Model builders and SAs
What would your ideal solution be? How would it add value to your current experience?
Please provide the ability to download the data in the New Modules Experience to a csv or xlsx
This allows MBs and SAs to continue to use the exports to analyse their model structures and write documentation.
On a typical project, this information would be downloaded multiple times a week to assess progress.
NB - Making the data accessible through an API is not a solution.
Please include any images to help illustrate your experience.
Re: Anaplan Workflow in action: Focused demo series
Hi @Dikshant, your message indicates you tested out some of these features a while back, and good news--there are now new product features available and more coming--there's an Anaplan Product team actively developing workflow features. I've provided a response to each of your clarifying points below.
- How does the backend end setup looks like for Submissions, Approvals and rejections setup for workflow? To get a better understanding of the backend setup required, I recommend you watch the August ACE community call between 6:53 - 21:00 for a simple example that uses decision tasks. That example uses the 'route by line item' feature to dynamically route decision tasks, and approvals and rejections are written back to the model in boolean line items. Anapedia and our community also has some other good material.
- What i feel is that the Notifications are all static, and cannot be dynamic based on backend line items. In the past year, Anaplan added the ability to route all relevant workflow steps by line item. For example, you can route decision tasks and notification tasks by line items. I hear 'line item routing' is the preferred method for routing because it can be very dynamic, especially when combined with features like 'skip approver'. The community event linked above demonstrates some of those new features.
- Also, we cannot customise the subject for email notifications. A couple months ago Anaplan added the ability to add context to emails. If the feature is enabled at the tenant level, email subjects are then customized with context related to the approval as shown in the example below. I heard the Product team is working to add more email customizations options soon.
Happy Modeling!
Display fiscal year label as FYXX/XX for cross year configuration
Hi,
My company is using a fiscal year that is not aligned to the conventional Jan-Dec period hence it will cross over the calendar year. In the Time settings, we can choose to align the fiscal year label to start or end month but the format is still FYXX. However it will be clearer if we can use a format like FY22/23 instead as it would align with our internal reporting and prevent any confusion for our anaplan users.
Thanks,
Peggy
Re: August 2025 platform releases and what’s next
Love the new Used on Page feature as well as the Page List Enhancements!!! Seeing Combined Grids make it to the "What's Next" section is so exciting!
To have search option in the beta version of Module
Hello Everyone,
I see that in the beta version of new module inventory, there are two issues:
- The Search icon is missing, which was there in the earlier version.
- When we use the find option (Ctrl +F), it only searches the module names present in the current screen and not from the entire list of modules.
Attached the pic for the same. I hope Anaplan support takes note of this and brings in the search feature in the Beta version of Module.
Thanks,
Praveen
Pro tips: Anaplan Lifecycle Management (ALM) implementation
Ahhh, the joys of reminiscing…unless you’re reminiscing about the early days of Anaplan, before Anaplan Lifecycle Management (ALM) was available and fully vetted like it is today. Back in my day — 2014 to 2020 to be exact — migrating changes in Anaplan meant just that. Migrating. Changes. Individually. Each. And. Every. One. It was a challenge.
Before ALM, my customers were always a little concerned with the concept of redevelopment because it was not (by definition) what they approved in the Non-Production environment. Sometimes, new functionality could be developed in Non-Prod, approved, redeveloped in Prod (but secured to the approvers), reapproved, and then deployed. Other times, when existing functionality was changed in significant enough a way to just create a new model, a data migration strategy was required to populate data from the “old” model into the “new” model. This, of course, had its own set of challenges.
If significant in-place model redevelopment was required, downtime would need to be scheduled with our customers, and my entire five-person team would come in on the weekend to make and validate the changes based on the business-approved Non-Prod model. Then we’d ask for validation and pray that the business-at-large would not find errors on Monday morning.
That all changed once ALM was ready to roll, and the early adopters had put it through the various flaming hoops of real-world scenario testing. So, you’re ready to make the leap?
What kinds of things should be considered when planning to implement ALM for a model?
- Time/Time ranges (does your model use them?)
- Development cycle (how frequently to have releases?)
- Segregation of duties and audit compliance controls (who needs documentation?)
Let’s dig in!
Time ranges
When considering time and time ranges in your models, it’s important to remember that these are structural elements within your model, the same as any other dimension or non-production list. With that said, it’s particularly easy to inadvertently lose data simply by rolling a model forward at year-end or changing the start or end date of a time range. Because any changes with respect to the Time Dimension will be included in a revision tag, it’s a good idea to experiment in a separate copy of your model to understand the end-state prior to making changes within your Non-Prod environment.
A good article on time/time range best practices is here: Best Practice: Time Range Application.
Development cycle
As of late 2020, time-related version settings (like switchover date, edit from, and edit to) became Production Data, which served to remove complicated interactions between normal monthly model maintenance and development work. Prior to that, the best practice was to strictly plan out deployment cycles to include one or more revision tags to “roll forward” a model’s switchover date and current period prior to starting the new development. This process was colorfully named “Back to the Future,” since the procedure required the workspace administrator to roll the model back to a state/time before the development started, sync the appropriate revision tag for the proper monthly version/time settings, and then roll the model back forward to continue development.
Even without the need to include the placeholder revision tags for monthly processes, the ability to revert model structures to a prior point in time defined by revision tags can be incredibly helpful. We’ve all experienced the scenario where a bug or other urgent change is reported that needs to be addressed. Instead of losing work or painfully scouring a model’s history for a change record to roll back to, Anaplan built on the “Back to the Future” concept to handle mid-development bug fixes. This ability to save the incomplete development state and resolve the request (and then get back to development) is described here: Save Incomplete Changes when Synchronizing in ALM. You can save your work in Dev, roll back the model, make the changes, sync to test, roll forward to where you started, and finish your development! It will become your next best friend soon enough!
Segregation of duties and audit compliance controls
Segregation of duties and audit compliance controls can also make a person crazy, however, ALM actually assists in that realm as well. Since ALM works across all workspaces in a tenancy, a user can be a workspace admin and act as a model builder in one workspace to perform development activities and be a standard end-user in the production model in a separate workspace. Here's a link to an article that explains how this works: Separation of Duties - Anaplan Technical Documentation. Development, deployment, and security can be entirely separate, allowing proper segregation of duties that may be required. In fact, Anaplan even provides a revision tag change analysis option (available beforehand and during each sync) that should satisfy audit and compliance teams requirements for details of the deployed modifications.
You may also ask if there is Application Lifecycle Management available for new UX apps; The answer is yes! It just looks a little different. There are now advanced capabilities to enable page builders to change source models associated with an app or individual page in an app, allow end users to choose between models within an app or page, and even create draft changes specific to ongoing model development to deploy later once the development is ready to sync. It’s also easy to duplicate or copy an app or page to make changes based on the initially deployed app that avoids needing to redevelop existing functionality. Remember, since new UX apps are a presentation layer that sits on top of a model, so long as the structural elements of the target models are the same, the same NUX app functionality will work from environment to environment. You can find that guide here: Application Lifecycle Management for the User Experience.
As always, Anaplan Community provides excellent opportunities for self-learning. A full set of guides on all topics ALM is available here: Application Lifecycle Management - Anaplan Technical Documentation.
Additionally, a three-part series to explain some specific key concepts around ALM is here: Application Lifecycle Management - Explained.
I also recommend taking a look at the full Application Lifecycle Management course in the Learning Center as well as the short courses available on Community:
- Anaplan User Experience (UX): Use UX Pages with Application Lifecycle Management (ALM)
- Course: Application Lifecycle Management (ALM)
Thanks for reading my blog! I hope you found it helpful. I wish you happy modeling and the best of luck in your ALM adventures!
Do you have any questions about Anaplan Lifecycle Management implementation? Leave a comment!
Check out recent Community blogs you may have missed:
- Overcoming the changing global supply chain with Anaplan
- Modeling in Anaplan with alternative tools: Part 2
- Headcount planning and attrition forecasting, enabled by Anaplan and PlanIQ
Re: August 2025 platform releases and what’s next
The addition of being able to see where modules are used in UX pages is such a welcome addition.
andrewtye
August 2025 platform releases and what’s next
Check out the latest Anaplan feature updates and enhancements in our August 2025 official release notes. The information below offers supplemental information to that post.
Planning experience
- Multi-browser tab syncing
When changing context or data on a UX page, you can now view real-time data updates across up to five visible browser tabs without refreshing, streamlining workflows and improving planning efficiency. This feature must be enabled by page builders in the Edit Selectors section under the Overview tab.
Multi-browser tab sync gif (page builder):
Multi-browser tab sync gif (end user):
Modeling and scalability
- New functions in Polaris
IRR (Internal Rate of Return) and NPV (Net Present Value) functions are available in Polaris, further increasing the breadth of domain-specific calculation capabilities available to users. ITEMLEVEL and HIERARCHYLEVEL, two new functions exclusive to the Polaris engine, have also been introduced, which will allow modelers to determine the level within a hierarchy of an item or list members. Modelers can easily use this information within their formulas, avoiding the need for more complex modeling constructs. - UX Page dependency data
In the modules view beta experience, model builders can now see which UX pages are linked to each module, improving visibility into dependencies and reducing the risk of unintended changes.
- Page List enhancements
The Pages Inventory has been enhanced to provide a more seamless and unified experience, aligning closely with the functionality of the New Modules Inventory. This includes a compact toolbar, page deletion, editable table columns, enhanced column sorting and arrangement, modules attribute column, and persistent right-hand panel tabs.
Data management and integrations
- Export to CSV in ADO
Inventory pages for connections, source data, and links can now be exported to CSV, along with datasets (both source datasets and those derived from transformation views). The files are exported in 500MB segments. Download is currently limited to only the first segment, which would typically be more than 1 million rows.
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.
Enterprise experience
- Combined Grids
We’re soon introducing Combined Grids, a new capability that lets page builders display multiple modules on a shared row axis within a single grid view. With Combined Grids, you can bring together data from multiple modules into one clear, unified grid. This means your teams can see the full picture in a single view, compare scenarios side by side, and make faster, more confident planning decisions - without the hassle of switching between modules. - Card settings enhancements
We are adding new options to Grid, Chart, Action, and KPI Cards that allow Page Builders to hide the maximize and comment features when not needed. This streamlines the user experience by showing only relevant settings, making pages cleaner and easier to navigate. - Undo for paste and delete actions
Users will be able to undo paste and delete actions directly in the grid using familiar keyboard shortcuts (Ctrl + Z for Windows, Cmd + Z for Mac). This reduces accidental data loss and boosts confidence and speed when making edits, as users can quickly revert changes without manual re-entry.
Anaplan Data Orchestrator (ADO)
- Dataspaces
The first release of Dataspaces enables users to segment ADO objects into separate partitions with user-level access controls. Integration Administrators can create private Dataspaces and share access selectively, enhancing security and governance. All current objects remain in the default Dataspace. Future releases will add dataset sharing and object copying between Dataspaces, improving collaboration and flexibility. - Improved Core Integration
The latest updates enhance scalability and performance for syncing data between Core planning models and ADO. It introduces support for referencing Saved Views (with specific dimensional requirements) when importing data, removing the need for action creation in models, which simplifies workflows. To leverage these improvements, users must define new source Datasets and Model Links, enabling more efficient and accurate data integration. - SFTP Connector
Available soon, this read-only connector supports secure file ingestion from SFTP using SSH key authentication. It handles CSV files with customizable separators, delimiters, and header configurations, supporting full, append, or incremental loads based on key columns or update timestamps. This flexibility allows customers to automate data loads from external systems efficiently. - Redshift Connector
Coming soon, the Redshift connector provides a secure, read-only connection to load data from Redshift tables and views using basic authentication. Similar to the SFTP connector, it supports full, append, or incremental loads with delta handling via cursor columns, helping customers streamline data integration from their cloud data warehouse.
Save the date for our October 29 platform release event!
During this session, we will explore the latest features from the past quarter, 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.
A link to register will be posted in Community at the beginning of October.
A function that identifies all saved views which filters are broken
I would like the function to identify all saved views which filters are broken(error).
Fujimura
CloudWorks: Stop hiding flows if model is archived or stop a schedule if flow was hidden
When a model is archived all related flows becomes hidden.
If, for testing purposes, there was a schedule set, it keeps running (and failing) in the background even though administrators are no longer able to see or change the flow.
One can always bring archive back and stop/change the flow, but it would be much easier if the scheduled process flows are still visible so they can be modified, stopped or repointed to proper model. Especially if workspace is occupied and you don't want to disrupt others work.
OR at least stop schedules if flows were hidden.
JJANIK