Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 29 Next »

To help you get a better understanding of any issues that emerge during the synchronisation of versions/components, the Version & Component Sync app has a conflicts feature. This feature creates a conflict whenever there is an issue during the synchronisation of versions or components. To make sure the app keeps working as expected it should be free of any conflicts.

Check your instance for synchronisation conflicts

  • Navigate to the Version & Component Sync page of your Source project

  • Check if any of your project links are in the conflicts status

Support-1 VCS (cloud).png
  • If so, click on the Linked project and navigate to the Conflicts tab

  • Click on Resolve to see details on how the conflict can be resolved.
    See a full overview of all possible conflicts and how to resolve them here.

  • If you can’t resolve the conflicts yourself send us a support request using our customer support portal.

  • Upon opening a support request please make sure to provide us with the following information:

    • A screenshot of the Conflicts page

    • A screenshot of the Conflict details

You can find a full list of all possible Version & Component Conflicts here.

Reset conflicts (Data Center only)

All conflicts that emerge during synchronisation are stored in a database table. This database table will be cleaned by a scheduled task the app runs several times a day. If you wish to reset the conflicts table manually (for example to make sure you only work on conflicts that are still present in your system) please use the following query:

TRUNCATE TABLE AO_687793_VCSCONFLICT

Note: You will not lose any important data by resetting the conflicts table

  • No labels