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
Anaplan currently provides the ability to create versions via an Import action, and update Version settings via an Import action. Ability to use an action (of any type, Import or otherwise) to do the following: - Rename Versions - Delete Versions Business Need: As we seek to continuously improve our planning process…
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 presenting visualizations in Anaplan, users often try to hover over lines/bars/points in the chart with their cursor to point…
Description Currently, scroll bars in Anaplan UX grids and cards only appear when content exceeds the visible area and when you hover over a card and the scroll bars appear. While this behavior is standard, it can create usability challenges for end users, especially when: Users are unsure if additional data exists beyond…
