A few years ago, there was a "live" model to model connection on the Anaplan roadmap. Has there been any update on whether models would speak to each other continuously versus through an import?
@3226899
I have been here for almost 9 years and don't remember that. Not saying it wasn't said, just that I don't remember it. To answer your question, at this time, I don't believe that is on our roadmap.
@3226899 I use Cloudworks for model to model integration. It is free, easy to use and smooth.
Thanks,
Misbah
Miz Logix
However, in general, model-to-model connections or interactions can still happen depending on the specific implementation and configuration of the models. For example, if two machine learning models are integrated into a system or pipeline and are designed to communicate with each other to perform a specific task, then a live model-to-model connection may be established.
In some cases, models may be deployed in a distributed manner across multiple systems or cloud services, and communication between the models may occur over network connections or APIs. In such cases, the latency and stability of the network connection may affect the real-time nature of the interaction between the models.
I'm working on a model with three versions: Actual (Actual version), Scenario: Prognose lopend jaar (current version), and Scenario: Budget volgend jaar. For one of the calculations, the Scenario: Prognose lopend jaar version needs to use a different current period than the Scenario: Budget volgend jaar. For this, Iβ¦
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-yearβ¦
