If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote.
Thanks!
@kjacokesYeah the decision between Versions and Fake Versions is always tricky, it's a bummer that we can't truly combine the best of both worlds. But if you submit it to the idea exchange let me know and I'd happily give it an upvote!
I have dug around and haven't seen any idea exchange requests that seem related.
Just to make sure I am up to date on my understanding of the current state: versions can be created via an import action, which can be saved and ran again to import more versions. However, the only way to rename or delete a version is via the Versions setting menu, there is no way to update it via a UX page or API. (As a sidenote, by my testing it seems that only a WSA can run the action to create Versions. Even if a non-WSA is full access or is marked with access to the action, they will get the message "You do not have access to run this action". This is similar to User list imports.)
You are interested in methods that would allow renaming and / or deleting Versions that could be performed from a UX page or triggered by the API, correct?
I assume that using fake versions is not an option in your case, as those could be controlled by an action.
All that to say, I think this would be valid idea exchange for you to submit! I imagine that there could be other model builders could benefit from the functionality. I know they have released improvements to the native User dimension recently.
thanks @NoahJ! yeah, good call-out. native versions just give us wildly better performance in a single model. and we do a lot of formulas like this to find a forecast version's most-recent budget version (to dynamically show a user the budget that a given forecast should be compared to). this is especially helpful if there's a mid-year re-budget and subsequent forecasts need to be compared to said budget. we've also committed to native versions for planning templates, so if we were to adopt custom versions and wanted the custom versions to follow us in context selectors across the app, we'd have to overhaul everything (which we may do someday), but for the time being this approach has worked well. my current hot take is we fall into a subset of customers for whom both approaches can work, just with tradeoffs to each.
@NoahJ , here you go! https://community.anaplan.com/discussion/161239/ability-to-rename-delete-native-versions-via-import-action/p1?new=1
Appreciate the responsiveness and support!
Hi everyone 👋 If you build or maintain Anaplan models, you've probably hit the same walls I kept hitting. Some basic questions about a model's structure have no single screen to answer them. You end up clicking through modules and pages one by one, or writing API scripts just to get a list. These were the gaps that…
Hi Everyone, We have a requirement in Anaplan Consolidation & Reporting (Fluence) where the Entity Structure needs to change effective January 2026. The key requirement is that the existing entity structure should continue to be applicable for all reporting and consolidation periods through December 2025, while the new…
We've been building a tool called aplan4sheets and we'd genuinely like input from this community — both on what we've built so far and on what we should prioritize next. The problem we set out to solve: Anaplan's Excel add-in is Windows-centric, and there's no real native way to pivot Anaplan data in Google Sheets. We…
