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
We have discovered that Line Item Subsets cause unexpected behaviour in Polaris: their mere existence adds significantly to model size and calculation demand. This overhead is undocumented (it appears in neither Anapedia nor the Planual) and is not visible to the model builder during building. The only way to detect it is…
From my perspective, the Anaplan community has three purposes: Customers/Partners to share feedback with Anaplan so the roadmap can be designed with those who actually use—and pay for— the product(s) in mind. Status - Mixed success leaning towards failure— as of about 4 years ago, Anaplan stopped interacting with and…
Currently, when approvers are assigned dynamically from a module line item, a Decision Task proceeds as soon as any one of the assigned users approves it. Please extend the “Require approval from all assignees” option, which is currently available for manually selected approvers, to dynamically assigned approvers as well.…
