- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 06:37 PM
Hi all!
After resolving the skipped records (e.g., Reviewed and Merge), is the local record also updated to reflect the merged fields?
Because when I checked the update set, the local record did not update after the skipped record was resolved.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 06:43 PM
Hi @Lhora Alvarez ,
- Evaluate how you want to resolve the conflict for this record and take the appropriate action:
Action Description Retain the customized record as is and do not update it After reviewing the changes, set Resolution Status to Reviewed and Retained. The record moves from the Skipped Changes to Review to Skipped Changes Reviewed related list. See Review skipped records using related lists.
Retain the customization by merging changes from the updated object - Click Resolve Conflicts to navigate to the Resolve Conflicts form.
- Review the differences.
- To merge a field:
- Click the right-arrow button for the field.
- Click a text box to view and edit the detailed differences.
- When you have merged all appropriate fields, click Merge.
After merging the customization changes:- The Disposition changes from Skipped to Merged.
- The Resolution Status changes to Reviewed and Merged.
- The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list.
Discard the customization and update the record to match the base system for this upgrade After reviewing the changes, click Revert to Base System. - The Disposition changes from Skipped to Reverted.
- The Resolution Status changes to Reviewed and Reverted.
- The system creates a Customer Update record.
- The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list.
Note: At any time after you revert a customization, you can click Reapply Changes to reapply the customization (undo the revert).
Review the skip and perform no action on the object After reviewing the changes, set Resolution Status to Reviewed. The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list. Leave on the skipped list for a later decision, and note that you have not reviewed the record From the Resolution list, choose Not Reviewed to defer the decision on how to handle this conflict. The record stays on the Skipped Changes to Review related list. Note: The system tracks changes to records in an update set so you can apply these changes to another instance later. However, the system does not migrate the upgrade details records from one instance to the next. These records apply to a specific upgrade of a specific instance. If you want to preserve the Comments, Resolutions, or other information from the skipped list, export it from this instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 06:43 PM
Hi @Lhora Alvarez ,
- Evaluate how you want to resolve the conflict for this record and take the appropriate action:
Action Description Retain the customized record as is and do not update it After reviewing the changes, set Resolution Status to Reviewed and Retained. The record moves from the Skipped Changes to Review to Skipped Changes Reviewed related list. See Review skipped records using related lists.
Retain the customization by merging changes from the updated object - Click Resolve Conflicts to navigate to the Resolve Conflicts form.
- Review the differences.
- To merge a field:
- Click the right-arrow button for the field.
- Click a text box to view and edit the detailed differences.
- When you have merged all appropriate fields, click Merge.
After merging the customization changes:- The Disposition changes from Skipped to Merged.
- The Resolution Status changes to Reviewed and Merged.
- The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list.
Discard the customization and update the record to match the base system for this upgrade After reviewing the changes, click Revert to Base System. - The Disposition changes from Skipped to Reverted.
- The Resolution Status changes to Reviewed and Reverted.
- The system creates a Customer Update record.
- The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list.
Note: At any time after you revert a customization, you can click Reapply Changes to reapply the customization (undo the revert).
Review the skip and perform no action on the object After reviewing the changes, set Resolution Status to Reviewed. The record moves from the Skipped Changes to Review to the Skipped Changes Reviewed related list. Leave on the skipped list for a later decision, and note that you have not reviewed the record From the Resolution list, choose Not Reviewed to defer the decision on how to handle this conflict. The record stays on the Skipped Changes to Review related list. Note: The system tracks changes to records in an update set so you can apply these changes to another instance later. However, the system does not migrate the upgrade details records from one instance to the next. These records apply to a specific upgrade of a specific instance. If you want to preserve the Comments, Resolutions, or other information from the skipped list, export it from this instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 07:03 PM
@Community Alums
My concern is more on the local record rather than the Upgrade Details (aka Skipped Record)...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-20-2024 08:59 PM
Hi @Lhora Alvarez ,
Local Record's behavior will be as per your action taken during the resolving the Skipped records, as i mentioned in my previous answer.
The other local records will stay on the Skipped Changes to Review related list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-21-2024 05:49 PM
Let me leave this here...
Local record did not update even after the skipped record was reviewed and merged. In other words, the merged fields were not reflected on the local record.
To resolve this, we decided to revert it to base version instead.