Workspace Import/Export
Introduction¶
Workspaces and their structures can be exported and subsequently reimported using specific Export and Import functions.
The export function allows you to export, to files, the setup and potentially the data of one or several online Analytical Workspaces which have all datasets online and available to the user.
In particular, the data of several partitions associated with specific datasets can be exported. Users for whom function 0004173 is enabled are also able to delete the exported partitions from the source Analytical Workspace.
The export operation generates an encrypted file (.awex) with a maximum size of 2GB.
Note: in import/export operations, matrices comments and attachments are not considered.
Data validation¶
When the data import starts, the system checks that the selected files are correct and consistent.
| If... | Then... |
|---|---|
| it finds a blocking error (e.g. if the export has been divided into several files and these have not been imported simultaneously) | it displays details of the error and stops the update. |
| it finds a non-blocking error | it displays details of the warning and allows you to continue the update. |
There are the following possible non-blocking errors:
- The code of the Analytical Workspace present in the imported file does not match the code of the Analytical Workspace to be updated.
- The exported file was created in a different version from the one in which the import is being run.
- The exported file contains a table that is not present in the target environment.
- The exported file does not contain a table that is present in the target environment.
- The exported file contains a field that is not present in the target environment.
- The exported file does not contain a field that is present in the target environment.
In the absence of validation errors, the system displays a window summarising the validation operations.
Imports and user restrictions¶
When the import is performed on existing workspaces, if even one workspace is not accessible to the user due to restrictions on their user profile, the system will block the import and show a warning in the validation step.
When the import is performed on existing workspaces, if the user performing it has restrictions on datasets of the target workspace, the system will make any new datasets to be created available to the user provided that the restriction is defined at the workspace level and not directly on the individual datasets.
Where the import entails the addition of a new workspace, if the user has restrictions, the system adds the workspace to the list of workspaces available to be enabled on their profile.
For more details on restrictions, see .
Import¶
When the import entails an Analytical Workspace that is already present in the system, the system deletes the following elements before importing the data:
- the entire workspace setup, and the existing partitions and datasets
- data related to partitions not shared with the import file
Data related to partitions shared with the import file are retained. The data are validated before being imported.
Imported data source¶
The data to be imported can have the following sources:
| Source | Description |
|---|---|
| Client | The files are located in a local folder. |
| Application server | The files are located in a folder visible to the application server. Directory: folder (Writable folder) in which the files are located. See File name: name of the .awex file to be imported. |
| Endpoint/Tagetik Data Loader | The files are located at a CCH Tagetik Endpoint. See Endpoint/Tagetik Data Loader: Endpoint to be used Directory: sub-folder of the Endpoint at which the files are located. See File name: name of the .awex file to be imported. |
Note: the dynamic syntax can be used for the filename parameter: Multi File Syntax.In this case, since the files to be processed are AWEX archives, the syntax will not evaluate the contents of the ZIP/AWEX archives, but only the files themselves as entities.
Pre-import data validation¶
The data are validated before the import and any blocking errors are shown in the import window. If only non-blocking errors are returned, it is possible to proceed with the import. A non-blocking warning is returned if the exported file has at least one of the following characteristics:
- it was generated in a different version from the one in which the import is being run,
- it contains a table that is not present in the target environment,
- it does not contain a table that is present in the target environment,
- it contains a field that is not present in the target environment,
- it does not contain a field that is present in the target environment.
Import fields with Personal Data Protection¶
If the application manages GDPR/DAC6 regulations, it is possible to export the plain data from source workspace fields with the Personal Data Protection option active and, subsequently, recode them using the algorithm and key defined on the target environment. When the Personal Data Protection option is not active, the data are exported encrypted and are not visible if GDPR/DAC6 regulations are not managed in the target environment, or if the algorithm and key do not match those of the source workspace.
When the exported data is encrypted, the coding must be performed with the most recent algorithm supported by CCH Tagetik. Any data encrypted with algorithms related to less recent versions will cause problems in both the export and the import steps. In this case, data encrypted with old algorithms will be lost.
To check and encode data in a uniform manner, it is necessary to use the dedicated utilities offered by the Analytical Workspace. See Actions on personal data contained in the workspace.
Import and use of DB vendor Hana¶
When the work environment involves a Hana database and an analytical workspace is being imported, some partitions may occasionally become misaligned with the archive status of the scenarios/periods associated with the various processes to which the partitions belong. In this case, it is possible to realign the partitions from the process page via the 'Hot/Warm partition alignment' wizard - viewable with function code '004203' (See Archiving Process Data).