Import/ Export Analysis Models¶

During the deployment, DEV, UAT, and PROD environments are created in the Use Place. During each environment clone, the Setup Parameters need to be added.

How to Import Analysis Model(s)¶

Importing the Analysis Model is done via the Upload function on the Analysis Models page.

How to Export Parquet Data Source(s)¶

This functionality exports the Definition of the Data Source that can be imported into another Environment.

First, select Parquet data source entries on the Parquet Data Sources page.
Click Export.

The Parquet Data Source definition is exported to the local folder as a .json file.

Note

Ensure the number of Data Source entries that are selected for Exporting is the standard page size row count. The recommended page size is 24.

How to Import Parquet Data Source(s)¶

Click Import from the Parquet Data Sources page.

2.The Import Parquet Data Source page facilitates importing the file.

Data Properties:¶

Property	Description
Choose Parquet Data Source Definition (.json) file to be Uploaded	With the Browse option, the .json file can be uploaded (Parquet Data Source Definition). If the uploaded file requires to be changed, the Delete option deletes the uploaded file and another file can be browsed. Uploading .json file is a mandatory action.
Use Imported Parquet data source entries to Overwrite/Rename existing entries	By default, Overwrite toggle is ON. This option is a method of conflict handling. It enables updating if there are existing entries in the given specific environment that are also available in the .json (Parquet Data Source Definition) that will be imported. If Overwriting is not required, it can be toggled OFF via the option.

Upload the relevant Parquet Data Source Definition (.json) file.
Set the Overwrite toggle as required.
Finally, confirm the import of the file.

import_assisstant2_parquet

Successful completion is indicated in the Import Status section. Each individual imported Parquet data sources are listed with the status. Validation is done based on the Data Source ID and the related Database structure.

During the first movement between environments, the Import process will Insert all the Parquet Data Sources into the 2nd Environment, based on the exported .json (Parquet Data Source Definition) from the 1st Environment. Each entry status will be displayed as Inserted.

During any other movement between environments (after the initial), The import process will display the Import statuses accordingly, i.e.

if there are changes between the environments, required or the .json content is changed, each entry status will be displayed as Updated. If there are column changes, it will be validated.
if there are no changes between the environments, each entry status will be displayed as NoAction.

Import Status	Description
NoAction	Imported successfully, if there are existing entries(same Data Source ID), it is not updated
Updated	Imported successfully, if there are existing entries(same Data Source ID), it is updated
Inserted	Imported all the new entries successfully
Error	Import Errors

Note

If the content is changed in the exported .json file from the first environment, it is required to keep track of the local changes, as the changes are reflected in the second environment.

6.1 If the Overwrite toggle is set to false, Parquet data sources are not overwritten which indicates in NoAction status, but will insert new entries if available in the .json file (Parquet Data Source Definition) .

Import_parquet_noaction - Copy

6.2 If the Overwrite toggle is set to true; the parquet data sources are overwritten which indicates an Updated status.

Click Back to Data Sources to navigate back to the Parquet Data Sources page.

Event	Method
Import Analysis Model	Upload .pbix version via *Upload Analysis Model* page
Export Parquet Data Sources	Selection of the entry -->Click *Export*
Import Parquet Data Sources	Via *Import Parquet Data Source* Assistant