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:
When users export data from Anaplan Apps (CSV or Excel), the default file name is derived from the underlying module name or saved export definition, rather than from the App page or dashboard name the user is actively working in.
From the end-user’s perspective, this behavior is confusing and unintuitive. Business users interact only with the App interface and typically have no awareness of the technical module names in the background. As a result, the exported file name does not match what users see on screen or how they understand the data.
This issue is especially problematic when multiple App pages or dashboards are built on the same module. In these cases, exporting from different dashboards produces files with identical default names, even though the data context is different. Users then have multiple downloaded files with the same name and must manually open or rename them to figure out which is which.
Although users can rename the file during the “Save As” step, this is only a workaround. The default filename itself is misleading and causes unnecessary confusion, extra manual effort, and an increased risk of using the wrong file. We have received repeated internal feedback and complaints from business users about this behavior.
How often is this impacting your users?
- Daily
- Any time users export data from Anaplan Apps dashboards for reporting, analysis, or sharing
Exporting data is a core and frequent workflow for many users, making this a recurring usability issue rather than an edge case.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
- Business / end users (primary impact)
- Executive-level users exporting reports
- Analysts and planners using Apps for operational work
- Admins and model builders indirectly, due to increased user confusion and support questions
The impact is greatest for less technical users, who expect the system to reflect what they see in the App rather than internal model structures.
What would your ideal solution be? How would it add value to your current experience?
Ideal solution:
- The default export file name should automatically use the App page or dashboard name from which the export is initiated, rather than the underlying module name.
Optional enhancement:
- Provide a configurable naming priority, such as:
- App page / dashboard name
- Saved export name
- Module name (fallback)
Value added:
- Better aligns export behavior with how end users experience the system
- Eliminates confusion caused by identical default filenames across dashboards built on the same module
- Reduces manual renaming and extra steps
- Lowers the risk of users working with the wrong exported file
- Improves overall usability and adoption of Anaplan Apps, especially for business and executive users
Please include any images to help illustrate your experience.
