Generally, collisions may appear during the configuration pack import process. Their leading cause is that the dependent table or record does not exist in the database.

Consider a common use case:

  1. We have exported the Incident table, child for the Task table.
  2. We import it to the instance without the Task table.
  3. In this case, the Incident table cannot be created on the target instance, because there is no parent table from which to inherit.

After that, you can find the erroneous record at the VCS preview log related list (in the VCS Retrieved Pack section). This record has the state = collision and the appropriate Error Text containing the error cause. Erroneous records cannot be included in the saved records pack (VCS Records) bound to the retrieved pack that is used for data recovery.

Collisions disposal methods

The idea in the collision fixing process is to try to dispose of collisions in the highest level tables. This method allows removing collisions in the lower-level tables automatically. It can be done about like this:

  1. Filter the records in the VCS Preview Log by the state (state = collision).
  2. Analyze errors for the records at the top of the list.
    1. Alternative way: you can filter the list by the Table field. The highest-level tables to analyze are, for example, sys_db_table, sys_number, sys_db_column, and some others.
  3. After the error cause was found, it must be fixed on the source instance. The configuration pack is to be exported and previewed again by clicking Preview Again Local Pack.
  4. If collisions are gone, then this configuration pack can now be imported. Herewith, all the records from the last configuration pack attached are imported. The retrieved pack status changes to Loaded. The records are added to the VCS Record (sys_vcs_record) table. The last preview log is available in the Related Lists area.
  5. After importing, the retrieved pack applying possibility appears. For this, click Apply Local Pack. The system restores records from this configuration pack (in other words, from the VCS Record (sys_vcs_record) table records attached to this retrieved pack). The retrieved pack changes its state to Committed.
  6. If the collisions are not gone, then return to the previous steps.

Collision case 1

When installing a configuration pack in the system, some record “X” is added. At the same time, it is referenced to another records “Y” in this system and in this configuration pack. Both records that the record ‘X’ is referenced to do not exist. When the export admin initiates a configuration pack preview (using a Preview Local Pack button), the collision is thrown on this record, which is an expected result.

Collision solving:

The solution is the configuration pack rebuilt in order to get the record “Y” into it.

Collision case 2

The 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 initiates a configuration pack preview (using a Preview Local Pack button), the collision is thrown on this record, which is an expected result.

Collision solving:

The solution is the configuration pack rebuilt in order to remove this record from it.

Collision case 3

Create a table in the source instance, with the field number equal to N.

Create the same table with the same name in the target instance, with the field number equal to N-1.

In the source instance, perform the export of the table fields into a configuration pack, after that download a .SOP file and unpack it in the target instance.

The result will be a collision thrown, and a message that this object is not valid, any actions on it cannot be taken.

Collision solving:

To solve this collision, create or update the object, excluding attributes missing on the target instance. In the above example, the N-fielded table will be successfully imported to the target instance, where the (N-1)-fielded table is created. But, the fields that exist in the source instance and are not in the target instance will not be created in the target instance. See the schema below.

Collision case 4

The records on a target instance are newer than in a configuration pack to install. It can be determined by the date and time of record creation.

Collision solving:

Export admin needs to initiate a local pack preview. In the process:

  1. Collision-causing records will be marked with the Skipped state.
  2. When applying the local pack, the records with this state will be skipped. The records that were present on the target instance initially will stay.
  3. In the case of record in the configuration pack is newer than on the instance, then it will be marked with the Good state, and it will replace the record on the instance.

Collision case 5

A table being deleted from instance contains records (is not empty). If the table being deleted is empty, then there is no collision.

Collision solving:

  1. Collision-causing records will be marked with the Skipped state.
  2. When applying the local pack, the records with this state will be skipped.
  3. If the record was marked with the Good state, then the table will be deleted.

Collision case 6

A configuration pack contains objects related to the application X. At some moment, export admin tries to apply this configuration pack to the instance that does not have this application installed.

Collision solving:

The solution is  to rebuild the configuration pack in order to add records related to the missing application.

Collision case 7

Partial attributes mismatch between instances.

User case description.

Create a table on the source instance, with the field number equal to N.

Create the same table with the same name on the target instance, with the field number equal to N-1.

On the source instance, perform the export of the table fields into a configuration pack, after that, download a .SOP file and unpack it on the target instance.

The field names on source and target instances are slightly different. See the schema below.

Collision case 8

The collision cause is a unique key violation.

User case description

  1. It was discovered that the target instance (instance #2) contains incorrect translation record for some element (element #1) or does not contain any translation record. This record should be located in the Translations (sys_translation) table.
  2. This translation record for the element #1 has been created in an appropriate table on the instance #2.
  3. On instance #1 (the source instance), a .SOP file has been assembled containing translation for the element similar to element #1. The column_id, record_id and language_id fields necessary for UNIQUE CONSTRAINT forming matched up on both instances.
  4. This .SOP file has been uploaded on instance #2 like described above. VCS preview logs were generated.
  5. After loading a pack on instance #2, a collision VCS record appeared containing an Error Text more or less like this:
    1. "This record has a duplication of a unique key. DETAIL: Key (column_id, record_id, language_id)=(156941403909472422, 159170696512371798, 156628684306200767)."

Collision solving

The collision solving method is to decide which translation record is more up-to-date.

If an initial record located on the target instance is more up-to-date, then the collision record can be dropped from the configuration pack and not imported.

If a new record being imported is more up-to-date, then this record should be imported, what will cause initial record overwrite.