You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 4 Next »
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. Deleted records are restored, and created records are deleted.
After a rollback is completed, the imported versions remain in the system as non-current VCS records. You can restore these record versions manually if needed.
Example
- A configuration pack contains a record version X.
- Before import, the target instance had a version Y.
- After import of the local pack, 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:
- Navigate to Configuration → Local Pack.
- Open the local pack you need to rollback.
- Click Rollback preview to check the system's response to the record restoration.
- In the Related Lists area, open the VCS Preview Log tab.
- Filter out records in the Allowed state with the coundition builder, and process possible collisions if there are any.
- Click Rollback to restore the records to the previous version.
As a result, the following changes occur:
Import result | Rollback result |
|---|---|
| A new table | The table is dropped from the database, deleting any data from it. |
| A new field | The field is dropped from the database, deleting any data from it. |
| A deleted field | The field is restored to the database, but the original data is lost. |
| A record inserted | The record is deleted. |
| A record deleted | The record is restored with its original data. |
| A record updated | The previous record version is restored. |
Collision processing
General process of solving the rollback collisions is the following:
- In the configuration pack to be rollbacked, click Rollback preview.
- Scroll down to the Related Lists area and open the VCS Preview Log tab.
- Filter out the records in the Allowed state using the Condition Builder.
- Open one of the records. Find the information about the error in the Message field.
Make necessary changes to solve the collisions.
- Click Save or Save and Exit to apply changes.
- Return to the configuration pack record and click Rollback preview.
- Make sure that the VCS Preview Log record state changed to Good.
- Repeat the steps 3-8 until all necessary records in the VCS Preview Log are in the Good state.
- Click Rollback.
Collision cases
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 solving:
Move the current record to the local pack, which you need to rollback, and click Rollback preview.
Collision case 2
When rolling back a local pack, the state of the record is Collision. The Message field contains the following text:
Current record does not exist!
Collision solving:
Continue the rollback. The collision record will be skipped.
Collision case 3
When rolling back a local pack, the state of the record is Collision. The Message field contains the following text:
Previous version for current is not found
Collision solving:
Continue the rollback. The collision record will be skipped.
Collision case 4
The configuration pack contatins some records that should be inserted as new columns into a table. When rolling back a local pack, the records are 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.
Collision case 5
A local pack contains a new table as an Insert record. The rollback will cause the deletion of this table, but it contains one or more records. The state of the record is Skipped. The Message field contains the following text:
Table is not empty
Collision solving:
Open the list of the records of the table and delete all records manually.
See more examples of possible collisions in the Collisions processing article.
- No labels
