custom tables do not keep the datasets *1 after the model is saved
Posted: Tue Feb 05, 2019 7:42 pm
Hi
I join a simplistic model with two tables. the essai2 has the datasets named and the other has an *1 for the second table value. if one saves the model and one loads it again, the *1 has disappeared in the essai table, but not the named datasets in the essai2.
Of course, I suppose that you will not find the *1 that i saved, because it has disappeared.
You must just change the dataset for the second value in the table essai into *1, and the table essai will work correctly. But if you save the model and load it again, the *1 will have disappeared and the table essai will no more work correctly.
of course i can use the method with the dataset named, but in my case it was much more convenient to use the *1 formula.
I join a published VPM model that contains the two datasets current1 and current2.
the problem stays the same if you save the model as a .mdl file or in a published way as .vpm
I use Vensim DSS 7.3.5
Regards.
JJ
I join a simplistic model with two tables. the essai2 has the datasets named and the other has an *1 for the second table value. if one saves the model and one loads it again, the *1 has disappeared in the essai table, but not the named datasets in the essai2.
Of course, I suppose that you will not find the *1 that i saved, because it has disappeared.
You must just change the dataset for the second value in the table essai into *1, and the table essai will work correctly. But if you save the model and load it again, the *1 will have disappeared and the table essai will no more work correctly.
of course i can use the method with the dataset named, but in my case it was much more convenient to use the *1 formula.
I join a published VPM model that contains the two datasets current1 and current2.
the problem stays the same if you save the model as a .mdl file or in a published way as .vpm
I use Vensim DSS 7.3.5
Regards.
JJ