Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Identify customizations in widget related records

View and identify potentially problematic code in the widget dependencies, Angular Providers, and ng-templates that are being used by the widget.

Before you begin

Role required: admin or sp_admin

About this task

Your widget may be using potentially problematic code from any of the following records:

  • Widget Dependencies
  • Angular Providers
  • Angular ng-templates

You can view these related records directly from your portal page to check the code in each record.

Procedure

  1. Navigate to a portal page.

  2. On the page, open the widget context menu by CTRL+right-clicking any widget.

  3. On the widget context menu, click Show Widget Customizations.

    Widgets are color-coded as follows:

    ColorCustomization level
    GreenBase system widget
    YellowCloned widget
    BlueNew widget
    RedCustomized widget
  4. On any widget, click the information icon (

Image omitted: info-icon.png
Information icon\).
  1. On the window, open links to the following related records:
FieldDescription
DependenciesJavaScript and CSS files that the widget uses from the Widget Dependencies [sp_dependency] table.Note: The widget dependencies listed on this window only reflect the first-level dependencies. Any dependency that is nested deeper than the first level is not included. To further troubleshoot the widget, check the nested dependencies in the widget record.
Angular ProvidersAngular Providers that the widget uses from the Widget Angular Providers \[sp\_angular\_provider\] table.
Angular templatesAngular ng-templates that the widget uses from the Angular ng-templates \[sp\_ng\_template\] table.
Related records that you modified or developed are outlined in red.
Image omitted: outlined-in-red.png
Related records outlined in red
You can open each related record by clicking the record name.

What to do next

If you're still unable to diagnose the widget, consider checking nested dependencies or URL dependencies.