There is a development model DEV24 using which production model PROD24 was created.
Now I have created PROD25 model from PROD24.
If I create DEV25 using DEV24, would PROD25 and DEV25 be compatible with each other?
Hi @31MB ,
When you created PROD25, both PROD24 and PROD25 would be compatible with DEV24.
When you create DEV25, both PROD24 and PROD25 will be compatible with both DEV24 and DEV25, until the next sync.
The moment you sync PROD25 with DEV25, the ALM link between PROD25 and DEV24 will break. But PROD24 can continue to upgrade from DEV24, as long as it is not synced with DEV25.
In essense, any PROD cannot jump back and forth between multiple DEVs.
It would be a nightmare to maintain multiple DEVs, with time. Please check your model architecture if this can be avoided.
Cheers!
What's the #1 bottleneck in your Anaplan build cycle right now? A. Model documentation B. Onboarding new builders C. Optimizing slow formulas Curious which one takes the most time for your team and how you're currently addressing it.
If an AI agent could build your next Anaplan module from a plain-language prompt, would you trust it, or would you still rebuild it yourself line by line? Curious to hear how comfortable people would be with AI-generated Anaplan models and what level of validation you would expect before using the output.
The July and August releases added several useful capabilities to Anaplan AI, including the ability to create and retrieve saved views and create list import actions. It would be valuable to extend these capabilities to support the full end-to-end user story: creating a saved view and using it as the source for an importβ¦
