GET DIRECT DATA corrupted function

[geo_curious]

Hi,
I have had a data read in variable in my model sets for more than 2 years. I found out recently that with a recent modification of a .mdl file, reading in an old tab in an xlsx file that the GET DIRECT DATA() function simply stopped working for that .mdl file. I was puzzled, thinking that it was because of a .mdl modification that really had nothing to do with the GET DIRECT DATA() function, but I found that it was exclusively for that .xlsx tab that the function stopped working. In creating other similarly modified .mdls, the function works fine. I did model compares and found nothing of significance that was different. Is there anything that makes the GET DIRECT DATA() function fail commonly? I am asking to see if there might be some salvation for the file, or if I have to delete it and remake the .mdl.
No errors appear when running the corrupt GET DIRECT DATA(), it simply picks a number (on which basis I have no idea) and repeats it for all of model time, which renders the data import useless. Anyway, if there are no commonly known bugs/work arounds for this I will plan to rebuild the .mdl.

[Administrator]

Can you provide an example of this happening?

[geo_curious]

I have already saved over this .mdl file. The sequence to get this to happen was to first try running a grid search policy optimization, then run configuration with a save list, then run a regular single simulation without the savelist. On the last step the GET DIRECT DATA would not extract the xlsx information (but somehow came up with erroneous values) so that some dependent variables were all out of whack. A rewrite of the .mdl is working fine now.