Hi Anaplan,
It would be great for Anaplan to allow users to create alias names for: time, versions, modules, dashboard, list and lineitems.
Thanks,
Usman
Thanks for your idea Usman and for all the kudos! Can you please comment with some reasons why this would be useful for you?
What business process is this improving? What problem will this solve?
Hi @Rebecca
Most of the influence for this functionality comes from a usability and reporting perspectives, not modelling capability.
Users want greater flexibility in customising anaplan for themselves.
Some of the uses come from specifications our clients have:
- Centre of Excellence Naming conventions versus what some users actually - for example the coding of module names / lists may not be informative to a user in the same way it is to a model builder.
- Renaming list item names for a to user friendly names instead of codes
- Renaming the time dimensions to Jan instead of Jan 19
- Different Naming conventions for different business functions
I would also add that this would allow:
In general extend the display name concept to all structural elements
David
It would certainly be useful to have a unqiue identifer for line items that wasn't it's own name.
Having a "display name property" for each line item would allow us to duplicate names for line items which would be useful.
I +1 this idea.
Custom Naming for Time would be great as for instance maintaining a multi-language alias names
Hi @Miran and @Rebecca ,
Are there any updates on this ? I believe other tools like TM1 have this type of functionality as default.
I have seen several use cases where this functionality would really benefit from it.In a more recent process this is causing some "noise" and not so positive feedback from end users on their user adoption journey.
There are workarounds but this requires, IMHO, extra development and complexities that we would really like to avoid.
Thanks!
Alessio
Agreed, having the ability to change the display name of a line item in the UX would really improve reporting.
Bumping this back up—- Alias for line items and for time would be exceptional—
Use cases— line items— sometimes we need to 2 different line items in the same module for similar reasons but with different formulas (For a waterfall chart we need the formula to be a summary but a calculation may be needed for formulaic summary methods) — in this case we have two "ending value" line items that are both important to show but right now we need to add a non-sensical naming methodology.
For time— many users want to see "Start of Plan" and "End of Plan" rather than Q1 FY24. For consistent reporting not having the time change would assist other tools.
Having an alias that could be structural or "production data" would be a very helpful function and would not require logic references to change.
Are there any updates on this ?
As an Anaplan Tenant Administrator, I need the Export functionality to be able to export all the existing Tenant Level Roles information as well as the role details, into a CSV file, So that I have the accessibility to document and report to my security team. I know this feature is successfully implemented when I can see…
Currently, only Workspace Admins in Anaplan can access certain model metadata and deployment validation panels (such as Revision Tags, Data Tags, etc.) in the Production workspace. For security and compliance reasons, we want to avoid granting admin-level access to users who only need to view this information. There is no…
Currently, Anaplan does not natively restrict number inputs to specific ranges. Users can input any numeric value, which may result in data integrity problems, especially in collaborative or decentralised planning environments. Introducing a validation capability—where model builders set upper and lower bounds for number…
