- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2022 11:45 AM
Hi All,
With our Service Portal work, we try to avoid cloning widgets because any new platform features or fixes are only applied to the OOB version and it hasn't been easy to identify them without manually adding them during an upgrade to evaluate the widget changes.
Somewhere along the last year I found and ran a "report" that shows all SP widgets which are OOB, cloned, etc. This was part of something that we installed (I think?) in preprod that was wiped out with a cloneback. I remember showing it to our leadership to indicate the number of the cloned and modified widgets, and it had some way to show if it was OOB or upgraded with a recent platform upgrade. Now, I cannot find it. The closest I can find is the cloned widget table: sp_rel_widget_clone_list.do
It works, but is limited to admin access in preprod, so was hoping there was a way in production. Of course, I could have misremembered, but wanted to check with the community to see if there was something I was overlooking. We are currently on Rome and I recall it wasn't too long ago we saw this report.
thanks!
roger
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2022 11:59 AM
All custom updates for objects are maintained in sys_update_xml.LIST table.
You can query this table with sys_id of widgets to find out if these are customized.
Regards,
Sachin

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2022 11:59 AM
All custom updates for objects are maintained in sys_update_xml.LIST table.
You can query this table with sys_id of widgets to find out if these are customized.
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-07-2022 02:04 PM
Thanks Sachin,
It appears that my role can access that sys_update_xml table. It was not what I had remembered, specifically, but is a solution to my question and will work for me. Thanks!