Resolve Conflicts button is not available in the skipped record form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2024 10:22 PM - edited 05-09-2024 07:27 AM
Hi All,
Recently, during our Dev instance upgrade from Utah to Washington DC, we noticed some skipped records. Among them, we identified certain records with a disposition type skipped error. However, when we opened the skipped record form, we couldn't find the "Resolve Conflicts" button. It only appears when there's a disposition type skipped and skipped manual merge. Now, how should we review records with this skipped error disposition type?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2024 02:17 PM
I am facing the same issue when upgraded from Vancouver to Washington DC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 02:01 AM
We have the same issue. Is the intention that such conflicts are only to be resolved in the builder instance or post-upgrade in the consumer instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 07:05 AM
I can see that for some records button Resolve Conflicts is not available - can it be because you need to switch scope?
Another issue that I remember was that conflicts were not possible to solve - as a workaround we've received information to add/set system property mergetool.polaris ('true/false') to be set to false - and then try to see if possible to review conflict.
