Closed mabijkerk closed 9 months ago
The most important question is: (how) do we know which migrations have been missed?
Unfortunately it's not that straightforward to apply them. If values were changed based on older calculations we cannot see anymore what it should have been. We also don't know if some migrations have been carried out when the scenarios were updated (we migrate for 1 month after the last update), followed by some missed migrations when the scenarios were untouched again for a while, and then again maybe some applied migrations after an update.
Anyhow, we have to do it all by hand.
Did they create the scenario's through the API? Then they should have explicitly put keep_compatible
to true
like it says in our API docs. If they did not create them through the API, but via the font-end we have to investigate if that is the behaviour that we want - that scenario's get stale so quickly without users apparently being aware of it.
This issue also applies to the II3050v2 scenarios, though I'm still awaiting confirmation from our client to check that keep_compatible = false
was unintentional.
Closed in 7687e51
One of our clients has created a number of scenarios for which the
keep_compatible
attribute is set tofalse
. For the scenarios the attribute needs to be set totrue
. In the meantime, migrations have been applied that these scenarios have missed. The question is how to apply the missed migrations to the scenarios after they have been set totrue
. Perhaps this is done automatically by ETEngine?Scenarios are still confidential, so contact me for the scenario-links.
keep_compatible
for marked scenarios totrue
with an API callNotifying @DorinevanderVlies