Normally, when dealing with scenarios containing large numbers of data values, a modeller would create a scenario file with individual values saved literally, and array values saved by reference to whatever files they were originally loaded from. Sometimes, though, this is not the easiest approach, having two main problems:
When publishing a model with a scenario file like this, the file itself must be included along with all the other files referenced by it, and these must be installed in the same place in the directory tree relative to the scenario file as they were when the scenario was created
The process of loading values from a .csv file is quite time consuming, as the file has to be parsed and checked for syntax errors before the ASCII numerals can be converted into their actual values, and this has to be done every time the data is loaded.
So as an alternative, it is possible to have all the data saved in the scenario file, in a format that converts easily to the internal representation of numbers. For this to happen, when you load an array using any tab in the Table Data dialogue, you check the box labelled 'Include values in scenario file' before hitting OK. When the scenario file is subsequently saved (see Using the scenario file mechanism), the values will be saved along with it, and the files from which they were originally loaded will not be required again when the scenario file is reloaded. It will also reload very quickly.