Versions Compared

Old Version 10

changes.mady.by.user Anna Kryzhanovskaya

Saved on

compared with

New Version 11

changes.mady.by.user Anna Kryzhanovskaya

Saved on

Key

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

After loading a .SOP file into a retrieved pack record or after merging several local packs, some VCS records can thrown some errors. For example, in case records to be imported to the table translation records on the target instance are different from ones in the retrieved pack, causing data inconsistency or any other reason.N have different set of columns. 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.

You can find the erroneous record at in the VCS Preview Log related related list (of in the the VCS Retrieved Pack section). This record has the Collision state 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. records. Erroneous records are records in the following states:

StateDescription
CollisionRecord in this state requires user's attention and will not be implemented until the collision is solved. These records store the error cause in the Error Text field.
SkippedRecord in this state will be ignored while implementation. These records store the error cause in the Error Text field.
WarningThis state highlights valid records having minor mismatches. Depending on the error and user's actions, records will be implemented or ignored. These records store the error cause in the Error Text field.

You can solve some collisions by completing the following To resolve a collision, follow these steps:

  1. In the configuration pack you need, scroll down to the Related Lists area and open the VCS Preview Log tab.
  2. Filter out records in the Good state using the Condition Builder.
  3. Open one of the records.
  4. Read the text in the Error Text field to find the error cause.
  5. Open the relevant record in the Retrieved Records related list.

  6. Make necessary changes to the retrieved record in the 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.


  7. Click Save or Save and Exit to apply changes.
  8. Return to the configuration pack record and click Prepare changes.
  9. Make sure that the VCS Preview Log record state has changed to Good.
  10. Repeat these steps until all records in the VCS Preview Log are in the Good state.
  11. When all records in the VCS Preview Log are in the Good state, click Import pack.


Note

Please keep in mind that if any collisions occurred during the local pack preview, the process will be canceled on the first occasion, the others will not be shown.

Tip

If you correct the records on the source instance using the JSON Copy field, make sure to export the created local pack as a new application to save all the changes. It is necessary for saving the right configuration pack. This allows further use of the pack without throwing errors on other instances.

Collisions cases

The idea in the collision fixing process is to try to dispose of collisions in the highest level tables.

If a record can potentially be a 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 1

When 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 the pack by clicking Preview Local Pack, the collision is thrown on this record.

Collision solving:

The solution is to add the Y record to this configuration pack on the source instance.


Panel

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 previews the pack by clicking Preview Local Pack, the collision is thrown on this record.

Collision solving:

The solution is to remove change the X record from the configuration packstate to Skipped.


Panel

Collision case 3

Mismatch in the set of fields while importing records between alike tables.

Details:

  1. A The User table on the source instance has the N set of fields.
  2. The same User table with the same name on the target instance has the N-1 set of fields.
  3. When the export admin previews the pack containing records from the table with the N field set, the the collision is thrown, and a message that this object is not valid, any actions on it cannot be taken. The Error Text is the following: Column "manager" related to "user" does not exist.

Collision solving:

Continue import with the Warning state. In this case, the column will not be created, and the table imported records will have the N-1 set of fields.

Image RemovedImage Added


Panel

Collision case 4

The records on the target instance are newer than in a 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 the Skipped state. state. The Error Text is the following: The system has a newer record

Collision solving:

  • Change the state to Good. In this case, the target instance records will be updated to those from the configuration pack.
  • Keep the Skipped state to save the target instance records without changes.


Panel

Collision case 5

In 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: Table is not empty

Collision solving:

  • Change the state to Good. In this case, the table and all records will be deleted.
  • Keep the Skipped state. The table will stay as it is.


Panel

Collision case 6

A configuration pack contains objects related to the application X. The target instance does not have this application installed. The Error Text is the following: Related application "{application_id}" does not exist. Please repack this pack on the source instance

Collision solving:

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



Panel

Collision case 7

Partial attributes mismatch between instances. That is, equal tables have a difference in columns.

Details:

  • A table on the source instance has the N set of fields.

    • The

    same table with the same name on the target instance has the N-1 set of fields.
  • The field names on source and target instances are slightly different. See the schema below.

    • Collision solving:

    Continue import with the Warning state. In this case, the title column will not be created, and the source instance will keep the number column.

    Image Removed

    Panel

    Collision case 8

    The collision cause is a unique key violation.

    Details:

    1. The importing configuration pack contains 

    ___

    1. It was discovered that the target instance contains incorrect translation record for some element X 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 X has been created in an appropriate table on the target instance.
    3. On the source instance, a .SOP file has been assembled containing translation for the element similar to element X. 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 the source instance. VCS preview logs were generated.
    5. After loading a pack on the target instance, a collision VCS record appeared containing an Error Text more or less like this:
      • "This record has a duplication of a unique key. DETAIL: Key (column_id, record_id, language_id)=(156941403909472422, 159170696512371798, 156628684306200767)."

    Collision solving:

    Select a more relevant (correct or up-to-date) translation record:

    • If the initial record located on the target instance is more relevant, continue import. The system will ignore the collision record and the target instance record will remain unchanged.
    • If the new record is more relevant, then this record should be imported. The initial record will be updated.


    Table of Contents
    absoluteUrltrue
    classfixedPosition