Managing "Skipped Manual Merge" disposition for Store App plugin, upgrade recordsIssue 1) Login to the instance 2) Navigate to the Upgrade Center > Upgrade history and go into the Upgrade in question 3) Go into any of the records from Skipped Changes to Review, related list that have a Disposition of "Skipped Manual Merge" and are part of the plugin in question. 4) "Revert Copy to Base System", - Current behavior: "Operation not implemented" (in both the Global and plugin-specific scope) - Expected behavior: The record will revert to another version. CauseWhat is 'Skipped Manual Merged'?1. These skipped records must be from DELETE actions that were never created on our customer's instance, experiencing the issue. This indicates that these records were never created on the instance, but in the current version of the application, there are entries for deleting these records in the source instance.2. This could happen if the developer created the records and then deleted them in the same version. Which would mean that there is only one latest entry left in the application which is for DELETION. Hence, these records are in 'Skipped Manual Merged' state. Because there is no record in the instance it can delete.ResolutionAs these records never existed in the instance, there is no need for customer to review them. They can safely ignore them and simply mark all of them as either Retained OR Reviewed. They can either do that manually or using a script.Related LinksAs mentioned in #2 of the Cause section, these deletions were packaged into the application and published to store by the third-party vendor's team, These deletes are processed during the Application Install/Update as part of the "Author Elective Updates" folder.The customers can exclude these deletes during the installation by having the system property "com.glide.apps.include_my_deletes" set to "false". However, this can disable the "author elective updates" feature completely. There are few system properties to handle the DELETES while app install/update such as:- To only save and load Choice sets, set the system property com.glide.apps.include_only_sys_choice to true.- To allow automatically apply schema drops (automatically delete tables or columns that no longer exist in your application), set the system property com.glide.apps.include_my_schema to true.- To decide on a case-by-case basis, set com.glide.apps.force_skips to true. More details in the KB article: New York and Scoped Applications - some new features Third-party vendors can also exclude the deletes to be packaged into the application's first release version, by having the required author elective system properties set in the source instance. This will prevent records from being added to the author_elective_update folder if you have in-development applications on this instance which you intend to Publish.If it is a Store App customer, it can be raised with the vendor.