What is the best practice to review Skipped Records after upgrade

Aishwarya42
Tera Contributor

‎12-09-2022 12:12 AM

What is the best practice to review the skipped records in production? We have already reviewed and resolved them in lower instance and captured in an update set, shall we move the update set to prod or directly review the records in prod itself. Please share your views.

  • 8,491 Views
5 REPLIES 5

Vasantharajan N
Giga Sage
Giga Sage

‎12-09-2022 12:17 AM

As you would do production clone over the non-production instance before the upgrade, You need to apply the update set which you used to take action on the skipped records in the non-production instance, to production.


Thanks & Regards,
Vasanth

Community Alums
Not applicable

‎12-09-2022 12:22 AM

Hi @Aishwarya42 ,

If you customized or altered a record affected by this upgrade, such as a business rule or script, the upgrade generates a skip log record. You must resolve the differences between the upgraded and customized versions of the record by processing the skipped record list, or, in other terms, just processing the skipped list.

Before you begin

Role required: admin

About this task

Review the changes you made to baseline records, such as business rules and scripts, that appear on the skipped records list and revert to the baseline version if appropriate. Post-upgrade, thoroughly test all changes you made to these records.

Procedure

  1. If necessary, navigate to System Diagnostics > Upgrade Monitor.
    If the upgrade is still in progress, the system displays the Upgrade Progress screen. When the upgrade finishes, the system displays the Upgrade Summary Report.
  2. After the system displays the Upgrade Summary Report, click the Click here link in the Skipped box.
    The system displays the System Upgrades form.
  3. Navigate to Review Skipped Records section and – if necessary – scroll to the Skipped Changes to Review related list.
  4. Click the row for the first record you want to reconcile.
    The system displays the Upgrade Details form for that record.
  5. 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.
    Retain the customization by merging changes from the updated object.
    1. Click Resolve Conflicts to navigate to the Resolve Conflicts form.
    2. Review the differences.
    3. 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.
  6. In the Comment field, write the reasons for making your decision and other information you want to document.
  7. Click Update.
    Post-upgrade, thoroughly test all changes you made to the records on the skipped record list.

User271720
Tera Contributor

‎03-09-2023 08:58 AM

@Community Alums 

 

There seems to be an issue with the comments field here , so when you want to capture the Skipped Records on an Update Set so that you can move them to another instance , the comments are not getting captured and moved to the destination instance, 

0 Helpfuls

Community Alums
Not applicable
In response to User271720

‎03-09-2023 07:53 PM

Hi @User271720 ,

 Comments would never get captured in the update set. Please remember anything related to data would not get captured in the update set including scheduled jobs as well.