{"id":1370,"date":"2026-09-24T09:29:03","date_gmt":"2026-09-24T09:29:03","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/creatio\/?p=1370"},"modified":"2026-09-24T09:29:04","modified_gmt":"2026-09-24T09:29:04","slug":"disable-drill-down-creatio-indicator-widget","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/creatio\/2026\/09\/24\/disable-drill-down-creatio-indicator-widget\/","title":{"rendered":"Disabling Drill-Down on Creatio Indicator Widgets"},"content":{"rendered":"\n

If you build Freedom UI dashboards in Creatio, you use the indicator widget constantly. It displays a single key metric, such as total revenue or open support tickets. By default, clicking that metric opens the underlying record list.<\/p>\n\n\n\n

Sometimes that drill-down behaviour is helpful. Other times, such as on an executive summary page or a read-only dashboard, you want the number to stay static. You don’t want users clicking away to a section grid. This topic pops up often in the Creatio Community<\/a>. Several fixes circulate. Instead of just taking those suggestions at face value, we tested three common methods on an active environment to see what works.<\/p>\n\n\n\n

Here is what happened, including the approach that compiled cleanly but did nothing at all.<\/p>\n\n\n\n

The Test Setup<\/strong><\/p>\n\n\n\n

We set up a standard Freedom UI page (GrtxAnalysisHomePage) with an Indicator widget tracking Opportunity counts:<\/p>\n\n\n\n

{\n    \"operation\": \"insert\",\n    \"name\": \"IndicatorWidget_opportunity\",\n    \"values\": {\n        \"type\": \"crt.IndicatorWidget\",\n        \"config\": {\n            \"title\": \"#ResourceString(IndicatorWidget_title)#\",\n            \"data\": {\n                \"providing\": {\n                    \"schemaName\": \"Opportunity\",\n                    \"aggregation\": { \n                        \"column\": { \n                            \"expression\": { \"functionType\": 2, \"aggregationType\": 1 } \n                        } \n                    }\n                }\n            }\n        }\n    },\n    \"parentName\": \"Main\",\n    \"propertyName\": \"items\"\n}<\/code><\/pre>\n\n\n\n
Out of the box, clicking the widget navigates straight to the Opportunity section list. We ran our tests on an on-premise Creatio instance (version 8.1.4).<\/p>\n\n\n\n
    \n\n
  1. \nApproach 1: Setting drilldownEnabled: false<\/strong>\n
    The most straightforward fix recommended in community threads is adding drilldownEnabled: false<\/code> directly into the widget’s values array.<\/p>\n\n
    {\n    \"operation\": \"insert\",\n    \"name\": \"IndicatorWidget_opportunity\",\n    \"values\": {\n        \"type\": \"crt.IndicatorWidget\",\n        \"drilldownEnabled\": false,\n        \"config\": { ... }\n    }\n}<\/code><\/pre>\n\n
    What we observed:<\/strong>
    \nIt did not work. The page compiled cleanly without warnings. But in the UI, the widget remained fully clickable and still redirected to the Opportunity list.<\/p>\n\n
    Why it failed:<\/strong>
    \nA clean compile only means your JSON syntax is valid. It does not mean Creatio recognized the property. The original suggestion was reported working on version 8.3.4. On older 8.1.x builds, the crt.IndicatorWidget component simply ignores unknown configuration keys.<\/p>\n\n
    Verdict:<\/strong> Try this first if you run Creatio 8.3.x or newer. If you are on 8.1.x, do not rely on a successful compile. Test the button yourself in the browser.<\/em><\/p>\n<\/li>\n\n
  2. \nApproach 2: CSS pointer-events: none<\/strong>\n
    The second approach stops mouse clicks at the browser level using CSS. Rather than applying throwaway console styles, we packaged it into a clean module.<\/p>\n\n
      \n
    1. \nFind the Real CSS Selector<\/strong>\n
      Do not guess selector names. Right-click your indicator widget in your browser and select Inspect<\/strong>. Our element rendered like this:<\/p>\n\n
      <crt-indicator-widget element-name=\"IndicatorWidget_opportunity\">\n    <crt-analytics-widget>\n        <div class=\"analytics-widget-container\">\n            <span class=\"indicator-widget-metric-value\">1<\/span>\n        <\/div>\n    <\/crt-analytics-widget>\n<\/crt-indicator-widget><\/code><\/pre>\n\n
      Creatio uses element-name<\/code> as its standard DOM attribute for targeting specific Freedom UI components.<\/p>\n<\/li>\n\n
    2. \nCreate and Import the CSS Module<\/strong>\n
      To create the CSS module and import it into your page, follow the exact module creation steps covered in our earlier post on Managing Mandatory Fields in Creatio CRM<\/a>. In your module’s LESS tab, use the correct selector:<\/p>\n\n
      crt-indicator-widget[element-name=\"IndicatorWidget_opportunity\"] {\n    pointer-events: none;\n    cursor: default;\n}<\/code><\/pre>\n\n
      Then add the module dependency to your page schema’s define array:<\/p>\n\n
      define(\"GrtxAnalysisHomePage\", [\"css!GrtxIndicatorNoClickCss\"], function() {\n    return {\n        \/\/ Existing page configuration...\n    };\n});<\/code><\/pre>\n<\/li>\n<\/ol>\n\n
      What we observed:<\/strong>
      \nThe number remained visible, but mouse interactions stopped working completely. Hover effects vanished, and clicking did nothing.<\/p>\n\n
      Verdict:<\/strong> This approach is reliable and visually honest. The mouse cursor no longer hints that the widget is interactive. However, because it blocks all pointer events, you lose hover states entirely.<\/em><\/p>\n<\/li>\n\n
    3. \nApproach 3: Request Handler Override<\/strong>\n
      The third method intercepts the platform request triggered when a user clicks the indicator. This approach takes more code, but it leaves visual styles intact while disabling navigation.<\/p>\n\n
        \n
      1. \nAdd the Handler to Your Schema<\/strong>\n
        Open your page’s source code and insert a request handler into the handlers array:<\/p>\n\n
        handlers: [\n    {\n        request: \"crt.AnalyticsDataGridGetColumnsRequest\",\n        handler: async (request, next) => {\n            if (request.widgetAttributePrefix === \"DYN_IndicatorWidget_opportunity\") {\n                return;\n            }\n            return next?.handle(request);\n        }\n    }\n]<\/code><\/pre>\n\n
        When a user clicks the tile, Creatio fires crt.AnalyticsDataGridGetColumnsRequest<\/code> to build the list grid. By returning early, we cancel that request before navigation occurs.<\/p>\n<\/li>\n\n
      2. \nConfirm Your Widget Prefix<\/strong>\n
        In our testing, the attribute prefix followed the pattern DYN_<\/code> followed by the widget’s internal name. If you ever need to verify a prefix name, add a temporary console log inside your handler:<\/p>\n\n
        handler: async (request, next) => {\n    console.log(\"DEBUG request:\", request);\n    \/\/ ...\n}<\/code><\/pre>\n<\/li>\n<\/ol>\n\n
        What we observed:<\/strong>
        \nClicking the tile did nothing, and no errors appeared in the console. However, the element still looked like a hyperlink when hovered over.<\/p>\n\n
        Verdict:<\/strong> This gives you precise control over data navigation. To keep the UI honest, pair this handler with a simple CSS rule (cursor: default) so the cursor doesn’t trick users into thinking it is a link.<\/em><\/p>\n<\/li>\n\n<\/ol>\n\n\n\n
        Which Fix Should You Use?<\/strong><\/p>\n\n\n\n