SAM Pro - Revert Customization [samp_upgrade_skipped_files]

[James Rostron]

Hi Community,

We are beginning our SAM Pro journey with a client. We have undertaken an initial review of the system and identified a number of customised records that needed to be reverted. It was handy having the "Revert Customizations" module under the Software Asset module.

We have performed a clone (San Diego over Rome) over this weekend in preparation for starting this work and now the module is not finding these records and the list view is empty. Next Experience UI was also activated a day after the clone.

Fortunately I exported the list so I know exactly which records were identified and they are still on customised versions having checked a number of them today.

Why would the module have stopped identifiying these records since a clone?

Many Thanks,

James

[Mathew Hillyard]

From your question you imply that you have a production instance of San Diego, which you cloned onto a sub-production instance.

Did/does Production identify these records as customized? This module is just a list of "Software Asset Skipped Files" records. From the docs page on this, these are upgrade skipped files specific to Software Asset Management. As you've cloned from an upgraded instance, it seems likely that during a previous upgrade, some skipped files were reverted or something during an upgrade went awry and the corresponding sys_update_xml history is missing. Given this, it's likely you're now seeing whatever customizations there were in the Production instance, not your current sub-production instance.

[Jason Brough2]

Morning Mat, hope you are keeping well. Congrats on the CMA BTW.. Quick update..

We raised a call with SN about this so it is still ongoing. However, from taking another look, this is not a static list - it is dynamically created. Clicking on the 'Revert Customizations' module fires up the 'show_samp_skipped_files.do' processor, which fires up a script include function 'SampFindAllCustomizations().identifyAllOOBUpgradeSkippedDetails();'. Key to this is the 'sys_upgrade_history_log' table. This explains the few seconds delay while the list view is loaded. 

Oddly, when I clicked the link again yesterday, the records were generated again, so its not clear why they did not show for James but I am guessing there was as a result of some data changes.

As for the upgrade clone from Prod, the same skipped records are also in Prod, however we are seeing duplicate records for each skipped, so that is a question we posed to SN. We are just looking into their feedback now..

[Jason Brough2]

Quick update..

The Revert Customizations are now being created because the sys_upgrade_history_log was re-generated following a patch install recently. That explains one question above.

ServiceNow have suggested that we remove the sys_upgrade_history_log table from the exclusion list. This will remove the duplicates. Will need to test this after the next clone

[Mathew Hillyard]

Hey Jason, great to hear from you!

Interesting that the table is dynamic rather than static, but it makes sense given the results it must return

Sounds like it's just a wrapper table that goes and looks for SAM Pro customizations, pretty much liked a scoped check for SAMP skipped records during an upgrade. Also sounds like the duplicates and/or no results may have been as a result of the clone, so good to know about excluding the sys_upgrade_history_log table. 

Take care,

Mat