Make Versions a list format so we can use with LOOKUP logic based on user selections.
Would prevent the need for versions mapped to a pseudo-verison list with IF/THEN logic, ultimately reducing complexity and increasing ease-of-build.
I agree, this could help a lot of modelling where you want to map a version to a line item.
@usman.zia @Aleph
I agree this would be really useful in many different usecases.
Yes please! Great Idea @ablack & @Axel_H
Would be very useful! I have come across this many many times, wishing I could simply use versions as a format to be used for lookups.
This is the same as
https://community.anaplan.com/t5/Idea-Exchange/Ability-to-select-versions-as-a-list-formatted-line-item-for-use/idi-p/40198
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…
