Analytical Workspace Partition Version Update
Application Database > tile Analytical Workspaces > ( non-V2 workspace tile ) > 
> Update Version > OK on warning popup
Application Database > Navigation Panel > Analytic Information Hub > (workspace tile not V2 version) > > Update Version > OK on warning popup
IMPORTANT: The functionality is only accessible if the user has enabled 0004225 - Analytical Workspace migration.
Purpose of window¶
In this window, you can launch the version upgrade of an Analytical Workspace from the basic version (V0) to the version with Intelligent Analytics support (V2). This update enables the Analytical Workspace to perform reporting operations.
Unlike the other windows of CCH Tagetik, this window remains open until data processing is complete, and must be closed manually once it is finished (but, if desired, it can be closed earlier, letting the data processing continue).
Page fields
| Field | Description |
|---|---|
| Dataset | Description of the dataset to which the partition belongs |
| Partitions | Number of migrated partitions compared to total partitions. Updated in real time during migration. Only Reporting Layer partitions are counted. |
| Status | Status of migration. Updated in real time during migration. |
Actions on this page
| Element | Description |
|---|---|
| Update Version (Retry) | Run Version Update data processing. This changes the OID field of the datasets within the AW (and their reporting layer partitions) to an incremental numeric field, as well as updating the version number. During this operation, the other functions of the Analytical Workspace are blocked. Calculation Layer partitions are excluded from this operation, and will retain the alphanumeric OID. If the operation is somehow stopped before its completion, the Analytical Workspace and one of its datasets will fail. In that case, the 'Update Version' button is replaced by 'Retry', which restarts the migration from where it was left off. If one of the AW datasets is in the 'Err!Inconsistent Partitions' status, migration is not possible. |
Please note: if there are any ETL processes, stored procedures or special methods that insert data into the reporting layer partitions, these must be reviewed in order to remove the OID field.
On partitions that have been migrated to the version supporting Intelligent Analytics (V2), the OID field is managed as an auto-incrementing field and must not be set manually.