After loading a .SOP file into a retrieved pack record, some VCS records can throw errors. For example, in case the target instance has a newer record version than the importing pack. Generally, collisions may appear during the configuration pack import process.
Consider a common use case:
You can find the erroneous record in the VCS Preview Log related list of in the VCS Retrieved Pack records. These records store the error cause in the Error Text field and have the following states:
State | Description |
---|---|
Collision | Record in this state requires user's attention and will not be implemented until the collision is solved. |
Skipped | Record in this state will be ignored while implementation. |
Warning | This state highlights valid records having minor mismatches. Depending on the error, records will be implemented or ignored. |
You can solve some collisions by completing the following steps:
Make necessary changes to the retrieved record in the JSON Copy field.
In some cases, especially when the version records need complex fixes, it is preferable to configure the erroneous records on the source instance. |
If a record can potentially cause multiple collisions, the system will display only the first collision. Process the collision and click Prepare changes to see the next collision caused by this record. |
Collision case 1When installing a configuration pack in the system, some record X is added. At the same time, it references another record Y in this system and in this configuration pack. The Y record that the record X is referenced to does not exist. After loading the pack, a VCS record has the following Error Text:
Collision solving: The solution is to add the Y record to this configuration pack on the source instance. |
Collision case 2The record X is deleted from the system. At the same time, there is a reference to this record in the configuration pack. After loading the pack, a VCS record has the following Error Text:
Collision solving: The solution is to change the X record state to Skipped. |
Collision case 3Mismatch in the set of fields while importing records between alike tables. Details:
Collision solving:
OR
|
Collision case 4The records on the target instance are newer than in the configuration pack to install. It can be determined by the date and time of record creation. Collision-causing records will be marked with the Skipped state. The Error Text is the following:
Collision solving:
OR
|
Collision case 5In the configuration pack, a table is to be deleted but contains records (is not empty). Collision-causing records will be marked with the Skipped state. The Error Text is the following:
Collision solving:
OR
|
Collision case 6A configuration pack contains objects related to the application X. The target instance does not have this application installed. The Error Text is the following:
Collision solving: The solution is to repack the configuration pack on the source instance in order to add records related to the missing application. |
Collision case 7The collision cause is a unique key violation. Details:
Collision solving:
OR
|