How to update GCR version

Center of Excellence · October 2023

1. Abstract

As you may know, in Q2 2023 the first version of GCR, the new Board Solution to manage Financial Consolidation has been released.

Since then, the development of the solution is not finished, and new patch releases will be frequently released.

The goal of this document is to provide a guidance in how to update from your current GCR version to the latest available

2. Context

The GCR update version will be managed through a Transporter Package, here below you will find guidance in how to use this tool with a specific focus on GCR solution.

3. Content

3.1 Preliminary Instructions

First step needed is to clear these entities because they need to be reused in the latest version.

DB NAME	ENTITY NAME	ENTITY ID
GCR_LOG	Not Used	E_000218
GCR	Not Used	E_000276
GCR	Not Used 3	E_000338
GCR	Not Used 4	E_000339
GCR	Error List	E_000280

In the GCR patch release package you will find the folder “Application_Reset” and “Standard_Entities”.

Please take these two folders and replace them with the existing ones.

3.2 Snapshot

Go to “System Administrator” and click on “Data Model Snapshot” .

Click on “+ Snapshot” in order to create your Snapshot of GCR and GCR_Log Database and assign to the Snapshot a name as you prefer.

In the same package relase received you will also find a snapshot version.

Click un upload and select the snapshot from your folder:

3.3 Update GCR data model

The Core of the GCR solution is the GCR data model, so we will explain in detail how to update the GCR Database, then same approach can be used to migrate also the GC_LOG Database

In order to proceed, please select the 2 relative snapshot (The one provided by Board Team and the one created by You), After having selected them, please click on Transporter Package.

Please make sure that on the left as Source Snapshot you must have the one provided by Board, and on the right, as Target The snapshots created by you.

By default, the Transporter will take all the changes of the source Database and apply those to the target.

However, it may be that your Database has been customized in different ways. (For example, the use of some customizable cubes, entity or Data reader or for example modification of max item number of entities).

One fundamental assumption in order to be eligible to use the transporter is to not have created any Data reader, Cubes or Entities from the scratch, but instead have used the available ones of the Data model that are named as “Customizable”.

Having said that, before proceeding, unflag all the cubes, Entities and Data reader that has been modified compared to the standard version.

Click next, and you will find a check consistency button. Click on it.

Click next, and you will find a check consistency button. Click on it.

The possible results of this check are:

Success → If no errors are detected.
Error → A possible case when error appears is when the entity that have been unflagged is used in a cube.
Warning → A possible case of Warning is when you are replacing a cube that already contains data.

Next step is to assign a name for this Transporter Package and decide if flag or unflag the backup option. We warmly suggest keeping the backup option always flagged. Click Save in order to proceed.

You will find another screen with the list of all existing Transporter Packages. Consider only the one just created and click on Run in order to execute the update.

If everything works as expected, you will find the Last run log and the result as “Success”.

Please note that you may receive a warning message due to the cube “[CALC] - Adjustment for Hist rate.

The reason why you may receive this message is because this cube was already used in the consolidation process but is not an issue because it will be recalculated on every consolidation procedure.

3.4 Update GCR_LOG Database

Follow exactly the same process for the Update of GCR_LOG Database. Of course, make sure to select the right Database.

3.5 Update Version

After having completed the transporter package a last step is needed.

Open the capsule Admin, and navigate to the screen “Quick Configuration Wizard”.

Click on “Update Version”.

This procedure will:

Update the GCR version name;
Eventually update new Entities;

After having completed successfully all those actions, you will be able to use the GCR application taking advantage of the fix and enhancements of the patch release.

For any doubts or additional info related to the Transporter tool, please refer To the Board manual in the Transporter overview section.