Matches can occur when pushing content from an upstream project space to a downstream project space if there is content with the same name, ID, or label in both spaces (see the table below to elaborate). In this case, syncing between project spaces won't be successful. When you try to push from the upstream project space, you will receive an email informing you of the match, and when you try to sync content from the upstream project space, you will receive a warning message in the downstream project space. To resolve these matches, you have four options:
1. Rename the data model in either the upstream project space or the downstream project space.
2. Remove the existing data model in the downstream project space.
3. Select the Push & Overwrite Matches option when you push content from the upstream project space.
4. Select the Sync & Overwrite Matches option when you sync content from the downstream project space.
Please note that overriding matches may cause data loss and should be used with caution. Ensure you have a backup of the matching linked configurations before using this feature.
Match between upstream and downstream content:
Default Web User Role (e.g., App Builder)
When the two roles have the same Role Name but do not have the same permissions settings.
Custom Web User Role
When the two roles have the same name, the Role Name label.
When the two roles have the same Table ID.
Custom User Data
When the two have the same User Property label.
Case Update Rules
The two rules have the same Name.
Custom Location Data
When the two have the same Location Property label.
When the two have the same Keyword label
Web User Roles
When web user roles are synced from an upstream project space to a downstream project space, the Web User Roles are synced as a group. Default Web User Roles will not cause a match unless they have been edited and the permissions do not match. However, if a match with one Web User Role causes it to fail the sync, all other roles will not be synced. This means that if one role cannot be synced due to a match, all other roles in the group will not be updated in the downstream project space. Therefore, it is important to ensure that all roles are consistent between the upstream and downstream project spaces to prevent matches affecting the synchronization process.