Data publishing

Publish to database

You can now publish your model data to a local SQL database. The Publish to Database option has been added to the Publish Data dialog, while the file-based publishing formats are now part of the Publish to File option.

In the Publish to Database option you can specify a local SQL server, choose integrated authentication or supply your own credentials, and select the database to publish the data to.

You can publish data from multiple models, and multiple times from the same model, to the same database. Each set of published data is labeled with a unique ExportId value, allowing you to easily retrieve the desired data.

To create a new database, enter a name in the Database field and click Create. If the Create button is not enabled, a database with the same name already exists.

To remove an existing database, select it from the drop-down list and click Drop.

Publish to zipped CSV and Parquet files

Two new formats are now available in the Publish Data dialog when exporting your model data to file:

• The Zipped CSV Files data format saves data as multiple files in comma-separated values (CSV) format, which you can for example import into Microsoft Excel.

• The Zipped Parquet Files data format saves data as multiple Parquet files. Parquet is a column-oriented data file format designed for efficient data storage and retrieval.

In the Publish Data dialog available in the Model Explorer, you can choose a format by using the corresponding extension for the output file name, such as .csv.zip for zipped CSV files and .parquet.zip for zipped Parquet files.

In the Publish Data dialog available in the Plan and Network environments, you can choose any of the new formats from the Data Format list, as shown in the following image.

Other data publishing improvements

The following improvements were made to the published data:

• The CreatedDate and CreatedUser fields are now available for networks, having been added to each element of the Networks array. They were already available for single-plant cases in the Cases array.

• The details of RFG and CARB configurations are now reported as strings rather than numbers, making them much easier to interpret. For example, Season in RfgConfiguration is now Winter instead of 0.

• Resolved an issue that could cause the unit of measure of the reference density to be reported as null.