Versions Compared

Old Version 3

changes.mady.by.user Irina Grishina

Saved on

compared with

New Version Current

changes.mady.by.user Dina Baksheeva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Any completed local pack, including the uploaded imported ones, can be rolled back. A rollback restores the versions of all the records in this local pack as they were before the start of the update collection, in other words, before starting works on this local pack. When you roll back an imported configuration pack, the system is restored to the state before the import. Deleted records are restored, and created records are deleted.

After the a rollback is completed, the imported versions stay remain in the system as non-current outdated VCS records. You can restore these record versions manually if needed.

Example

  • A configuration pack contains a record version X.
  • Before the import, the target instance had a version Y.
  • After the import of the local pack is imported, the record version changed to X.
  • When you rollback the local pack, the Y version of the record is restored.

Rollback a local pack

To rollback a local pack, complete the steps below:

  1. Navigate to Configuration → Local Pack.
  2. Open the local pack you need to rollback.
  3. Click Rollback preview to check the system's response to the record restoration.
  4. In the Related Lists area, open the VCS Preview Log tab.
  5. Filter out records in the Allowed state with the condition builder, and process possible collisions if collisions if there are any.
  6. Click Rollback to restore the records to the previous version.

Here is the expected result of the processAs a result, the following changes occur:

Import result

Rollback result

A new tableThe table is dropped from the database, deleting any data from itand its records are deleted.
A new fieldThe field and the information about the field is dropped from the database, deleting any data from itdeleted.
A deleted fieldThe field is restored to the database, but the original data is lost.
A record insertedThe record is deleted.
A record deletedThe record is restored with its original initial data.
A record updatedThe previous record version is restored with its original data.


Collision

processing 

processing 
Anchor
collision processing
collision processing

General process of solving the rollback collisions is the following:

  1. In the configuration pack that you need to be rollbackedrollback, click Rollback preview.
  2. Scroll down to the Related Lists area and open the VCS Preview Log tabIn the Related Lists area, select the VCS Preview Log tab.
  3. Filter out the records in the the Allowed state using the Condition Builder state using the condition builder.
  4. Open one of the records.Read the text first record. Find the information about the error in the Message field to find the error cause.

  5. Make the necessary changes to solve the collisions.

  6. Click Save or Save and Exit to apply the changes.
  7. Return to the configuration pack record and click Rollback preview.
  8. Make sure Ensure that the VCS Preview Log record state has changed to Good Allowed.
  9. Repeat these the steps 3–8 until all necessary records in the VCS Preview Log are in the Good Allowed state.
  10. Click Rollback.

Collision

cases 

cases 
Anchor
collision processing
collision processing

Panel

Collision case 1

When rolling back a local pack, the state of the record is Collision. The Message field contains the following text:

The current version for this target entry is in a different local package. https://{your-instance.ru}/record/sys_vcs_record/123455521418546721

Collision solvingSolution:

Move the current record to the local pack

, which

that you need to rollback, and click Rollback preview.


Panel

Collision case 2

When rolling back a local pack, the state of the record is a record changes its state to Collision. The Message field contains the following text:

Current record does not exist!

Collision solvingSolution:

Continue the rollback. The collision record will be skipped.


Panel

Collision case 3

When rolling back a local pack, the state of the record is a record changes its state to Collision. The Message field contains the following text:

Previous version for current is not found

Collision solvingSolution:

Continue the rollback. The collision record will be skipped.


Panel

Collision case 4

The configuration pack inserted new columns into a table. When rolling back a local pack, a record is in the Warning state. The Message field contains the following text:

undefined column SQLERROR 42703

Collision solving:

Continue the rollback. The columns inserted during the import will be deleted.

Panel
Collision case 5

A local pack contains a new table as an Insert record. The A rollback will should cause the deletion of this table, but the records that it contains one or more records. The , prevent the table from removal. When the rollback is prepared, the state of the record is records changes to Skipped. The Message field contains the following text:

Table is not empty

Collision solvingSolution:Open the list of the records of the table and delete all records manually

  • Set the state as Allowed to remove the table and its records.
    OR
  • Keep the state Skipped unchanged, the table will remain in the system.


Tip

See more examples of possible collisions in the Collisions processing Collision Resolving Rules article. 


Table of Contents
absoluteUrltrue
classfixedPosition
printablefalse

.

Panel
  • Configuration Packs
  • Assembling and exporting local packs
    • Importing configuration packs