multiple developers are working on different enhancements to the same model


We have two approaches to manage scenarios where multiple developers are working on different enhancements to the same model, and we need to push their changes separately into the production model:

1. Rollback Method:

  • After completing a build in the development model (in standard mode), the developer meticulously documents all changes made during the build process.
  • They then roll back the model to a previous revision tag history ID that aligns with the current production model.
  • Following the documentation, they rebuild only the changes intended for production.
  • Once this targeted build is complete, they create a new revision tag, push those specific changes into production, and roll forward the history ID to the rollback ID. This allows developers to seamlessly resume their individual builds.
  • Crucial Notes:
    • Clear communication among developers is paramount to prevent unintended changes during the rollback state.
    • Exhaustive documentation of every aspect of the build is essential to avoid discrepancies when pushing to production.

2. Dormant Method:

  • Each developer creates a manual Boolean line item (e.g., "P12 build") and bases their entire enhancement on that Boolean.
  • For example, when pulling sales data into a line item and performing subsequent calculations, the formula could be written as: If P12 build then Sales ELSE 0. This ensures the build remains dormant and doesn't impact the production model until the Boolean is activated.
  • Key Considerations:
    • This method might not be ideal for large models in classic Anaplan, as it could potentially strain production workspace capacity.
    • Developers must have a clear understanding of their build plans and the ability to make it Boolean-dependent.
    • Impact analysis is highly recommended before commencing, as most enhancements are add-on features that rely on existing builds.
    • Saved views should also incorporate the Boolean line item as a filter to prevent unintended actions.

Ultimately, the chosen method depends on your specific project needs and model complexities. Whether you rewind and rebuild or plant dormant seeds, remember: communication and planning are the fertilizer that keeps your model garden thriving!

What are your thoughts on these approaches? Have you encountered similar challenges? Share your experiences in the comments below!

3 votes

New · Last Updated

Get Started with Idea Exchange

See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!