Ability to select versions as a list formatted line item for use in lookup statements

Options
ron_baylo
ron_baylo Member, ALL USERS, Community Member Posts: 3 Master Anaplanner of the Year
in Planning & Modeling

Versions are useful as they allow switchover functionality enabling a user to both enter a forecast on a line and see actuals in the same line item. However, comparing versions to eachother (any version to any other version dynamically) requires a "Versions List" and logic to engage that list with the Version you want to pull with [SELECT:VERSIONS.(verions name here]. If Version could be a format of a line item, then Anaplan reporting out of version would be greatly enhanced as these version formatted line items could be used in Lookup statements.

Tagged:

Comments

  • achout
    achout Member, ALL USERS, Partner, Community Pioneer Posts: 2 Master Anaplanner of the Year

    Hi All, some good news...

    This has been put on the long-term roadmap, see link below.
    But the short term list wouold be nicer. Maybe by consolidating kudos, because saw several similar request..

    https://community.anaplan.com/t5/Idea-Exchange/Add-Versions-as-a-native-option-for-a-line-item-property-format/idi-p/34482

    Thanks a lot!

    Alexander

  • dkangrga
    dkangrga Member, ALL USERS, Community Member Posts: 5 Occasional Contributor

    following.

  • mpeck
    mpeck Member, ALL USERS, GroupMember, Community Member, Community Pioneer Posts: 5 Master Anaplanner of the Year

    +1 please add

  • tompatrickting22
    tompatrickting22 Member, ALL USERS Posts: 5 New Contributor

    need this one. +1 vote

  • mpeck
    mpeck Member, ALL USERS, GroupMember, Community Member, Community Pioneer Posts: 5 Master Anaplanner of the Year

    Status check: 156 votes and was submitted 3 years ago. This functionality is still needed.

  • OliverIbach
    OliverIbach Member, ALL USERS Posts: 5 Occasional Contributor

    It is quite unsatisfying that this feature is still pending. The most likely proposed solution for that problem is to build a own version dimension and use this instead. But the consquence of that would be the disability to use build in functions, like switch over date and formula scopes. Additionally this would practically eliminate any future use of an official feature based on the official  versions, since that would need a complete rework of the custom solution.

     

    In conclusion we decided to go with the official version list, to hardcode those usecases and pray that anaplan will receive an official update.

  • maud_vermeulen
    maud_vermeulen Member, ALL USERS, GroupMember, Partner, Certified Model Builder, Community Pioneer Posts: 5 Master Anaplanner of the Year

    Indeed, it means that in most cases you have to use a custom version dimension, while the switch-over functionality is promoted. We always have to explain why we are not using it.

  • jpause
    jpause Member, ALL USERS, GroupMember, Partner, Certified Model Builder Posts: 5 Contributor

    I second the recent comments and would like to add...  come on man. 

     

    This limitation ultimately leads to more implementation time on EVERY SINGLE PROJECT.  This means all implementations estimates are up to cover this which makes us less competitive. Beyond that basic point there is the issue of ongoing usability and maintenance for a system riddled with snapshot modules.

     

    Which drives me to the last point. As long as we are addressing this, could we also address the inability to pass formatting or summary configuration through a LISS refenced module.  This also creates complexity in all snapshot variance modules. 

     

    "Come on baby light that fire"

           ~The Doors

     

     

  • Ron Baylo
    Ron Baylo Member, ALL USERS, Partner, Certified Model Builder Posts: 5 Occasional Contributor

    For those with the opportunity to do so,  choosing a version list approach should be considered. "Switchover" is handled by version list item with end user selections that do not require workspace admin paired with DCA lock logic. The only real drawback being extra line items in modules for Actual and Forecast but this also enables a point of comparison of Actuals versus Forecast that is not possible with standard Switchover.

  • CommunityMember111481
    CommunityMember111481 Member, ALL USERS, Partner, Certified Model Builder Posts: 5 Occasional Contributor

    -> Ability to select versions as a list formatted line item for use in lookup statements.
    Another vote for this. Having this will help even in big sized versioned modules avoiding additional modules for variance analysises.

  • clark.earl
    clark.earl Member, ALL USERS, Community Member Posts: 2 New Contributor

    Seeing that this request is 3.5 years old, maybe Anaplan could at least update the training and demos to emphasize that the native versions functionality is a legacy feature that is no longer actively supported.  There is almost no situation where the native versions are the right choice long-term, but that's what's sold to the client because it's faster to demo.  By the time the new customers realize the inflexibility of the native versions, they've incurred a lot of technical debt.

  • OliverIbach
    OliverIbach Member, ALL USERS Posts: 5 Occasional Contributor

    @rob_marshall 

    The point of the discussion is, that besides all the feature native version have, the limitation of not beeing able to use them as list formatted line item, renders them nealry unusable.

     

    If there has been no substantial change to native versions, despite the fact that the lag of one feature is causing massive modeling problems in nealry every project, someone can come to the conculsion, that this feature is no longer in active development.

     

    To your links: first link outlines the discussed limitation but not its implication, last edit 2020. Seccond link is newer, great technical detail, makes me want to use native version for technical reasons, but does not relate to the discussed problem.

Categories