Loading a saved set from a global in 2.1.2

Classic Servoy
1

Some queries regarding apparent changes in behaviour in 2.1.2 in relation to saved sets in globals:

I often save a set of records in a global field using ```
globals.temp_set = controller.duplicateFoundSet()


In versions prior to 2.1.2 I found that it was necessary to convert the set in the global into a dataset before it would load correctly

var dataset = databaseManager.convertToDataSet(globals.temp_set);
controller.loadRecords(dataset);


In 2.1.2 this no longer works, but loading the records directly from the global field now does work <img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" /> EXCEPT... if the global is pre-defined in the field definitions then re-loading the records from the global does not work (the error seems to be requesting a full 'SELECT...' statement). Up til now the global HAS existed in the globals field definitions and this has never been a problem. (I think I recall reading in the docs that globals should be defined in the field definitions)

In 2.1.2, if I remove the global field definition and simply declare and use the global as a variable when required, then saving a set and re-loading it from the global works fine.

Can anyone confirm that there have been changes in 2.1.2 that explain these apparent behaviour changes?
2

As far as I know (Jan told me a while ago) that controller.duplicateFoundSet() is suitable only for variables and NOT in conjuction with globals.

Do not know the reason exactly.

3

thanks for that - and yet up til now it has been working fine :? and why does it still work in 2.1.2 if I dont define the global in the field definitions, but simply declare and use it when I need it? - is the global used in this way actually behaving like a true (global) variable?

If globals cannot be used at all in this way, what is the best alternative given that I want to store the current set of records for possible restoration later?