Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
After loading a .SOP file into a retrieved pack record, some VCS records can throw errors. For example, in case records to be imported to the table N have different set of columns the system checks if VCS records may cause errors. Generally, collisions may appear during the configuration pack import process.
Consider a common use case:
- We have exported the Incident table, child for the Task tablea Business Rule record.
- We import it to the instance without the Task table.target instance which has the same Business Rule record updated later, that is, this record is newer.
- The collision is thrown: the target instance has a newer version of this recordIn this case, the Incident table cannot be created on the target instance because there is no parent table from which to inherit.
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 theError TextMessage 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 implementationimplementing the pack. |
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:
- In the configuration pack you need, scroll down to the Related Lists area and open the VCS Preview Log tab.
- Filter out records in the Good state using the Condition Builder.
- Open one of the recordsa record from the selection.
- Read the text in the Error Text field the Message field to find the error cause.
- Open the corresponding record in the Retrieved Records related list.
Make necessary changes to the retrieved record in the JSON Copy field.
Tip In some cases, especially when the version records need complex fixes, it is preferable to configure the erroneous records on the source instance and try to implement fixed configuration pack once again.
- Click Save or Save and Exit to apply changes.
- Return to the configuration pack record and click Prepare changes.
- Make sure that the VCS Preview Log record state has changed to Good.
- Repeat these steps until all necessary records in the VCS Preview Log are in the Good state.
- When all necessary records in the VCS Preview Log are in the Good state, click Import pack.
Note |
---|
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. |
Collisions cases
Panel | ||
---|---|---|
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. When the export admin previews After loading the pack by clicking Preview Local Pack, the collision is thrown on this record., a VCS record has the following Message:
Collision solving: The solution is to add the Y record to this configuration pack on the source instance. |
Panel |
---|
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. When the export admin previews the pack by clicking Preview Local Pack, the collision is thrown on this record.After loading the pack, a VCS record has the following Message:
Collision solving: The solution is to change the X record state to Skipped. |
Panel |
---|
Collision case 3Mismatch in the set of fields while importing records between alike tables. Details:
Collision solving:
OR
|
Panel |
---|
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 Message is the following:
Collision solving:
OR
|
Panel |
---|
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 Message is the following:
Collision solving:
OR
|
Panel |
---|
Collision case 6A configuration pack contains objects related to the application X. The target instance does not have this application installed. The Error Text Message 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. |
Panel |
---|
Collision case 7The collision cause is a unique key violation. Details:
Collision solving:
OR Repack the configuration pack so that the X1 record has all field values matching the X2 record
|
Panel |
---|
Collision case 8The column to be inserted exists on some level of inheritance. Details:
Collision solving: The solution is to change the X record state to Skipped. |
Table of Contents | ||||
---|---|---|---|---|
|
/
Panel |
---|
Related articles |