Enhance ALM to pick and choose objects to sync with production


Description of the enhancement required:

Enhance ALM to pick and choose objects to sync with production


An example of the enhancement:

Currently, we are not able to move only few selected changes from development to production. The model sync will move all changes as on a revision tag. Requesting development team to explore options of extending the ALM functionality to move only few required changes to production.


A story for why you want the enhancement:

Larrge customers will have multiple teams working on different projects within Anaplan models. Each project will have different timelines and may go-live at different time. If ALM is enhanced to sync only required objects to production, then multiple projects can run parallelly and have different timelines and go-live dates.

Community Manager
Status changed to: Considered for Future Roadmap
Certified Master Anaplanner

This has become a major issue for our team, as one group of model builders fix Production defects while other developers do sprint work in parallel. We need this functionality in order to push work that resolves defects raised by users, while protecting the Production model from untested or partially tested user stories.


Is there potential for this update to make it on the roadmap fairly soon?

New Contributor

I think this is a required feature for any enterprise ready tool, any idea when we can expect this feature to be GA

New Contributor

This would be a significant enhancement to reduce the amount of time our team needs to spend on deployment of enhancements and new code.  Not having the ability to selectively package and push code restricts our ability to deliver timely updates for our end users.  Any time we need a large change it holds up all other enhancements and is one of our biggest pain points with Anaplan that effects our end user adoption and satisfaction.  

New Contributor

This would help our team and other customers who need to selectively push changes to production.

New Contributor

This really needs to be prioritised.  We're either having to significantly delay fixes or having to redo a lot of work multiple times.

Occasional Contributor

We're just putting together our development workflow, and I'm really surprised that branching and segregation of feature development isn't already possible. This really impacts the ability to build parallel features in the same model or carry out bug fixes.

New Contributor

That's a great idea. Currently, we have to make copy of DEV where we do model building - after we agree approach to certain user story we need to move changes manually to original DEV model while keeping in mind that we could be in a spot where we have development done in DEV which we would like to move after current reporting period but there is a bug in production that have to be fixed ASAP which forces us to move previous development as well.


Really coplicates our approach to model building.  

Users Online
Currently online: 164 members 759 guests
Please welcome our newest community members: