How to Show a Secondary Value in Indicator Based on a Date Filter

[Liliia_DevX]

How to Show a Secondary Value in an Indicator Based on a Date Filter

This article provides an example solution on how to show a secondary value in the Indicator widget based on the date filter.

This allows you to have multiple dashboard filters but shows the secondary title and value only if the date and time filter is enabled. If it’s not and/or there are other filters enabled then the secondary title disappears.

See it in action below:

How to use it?

1. Create an Indicator widget and add a value.
2. Add a secondary value.
3. Press the 3 dots menu and choose "Edit Script".
   
   
4. Paste the following script and press "Save".

widget.on("processresult", function (widget, query) {
    opMap = widget.indicatorInstance._optionsMap["numericSimple"];
    const { secondaryTitle, secondary } = query.result;

    const secondaryTitleText = secondaryTitle.text;
    const secondaryValue = secondary.text;
    const dashboardFilters = prism.activeDashboard.filters.$$items;

    const dateTimeFilter = dashboardFilters.find(item => item.jaql.datatype == "datetime");
    const otherFilters = dashboardFilters.filter(item => item.jaql.datatype != "datetime");

    if (dateTimeFilter) {
        const hasEnabledOtherFilters = otherFilters.some(filter => !filter?.disabled);
        const isDateTimeFilterDisabled = dateTimeFilter?.disabled;

        if (hasEnabledOtherFilters || isDateTimeFilterDisabled) {
            secondaryTitle.text = '';
            secondary.text = '';
            opMap.borderColor = 'transparent'
        } else {
            secondaryTitle.text = secondaryTitleText;
            secondary.text = secondaryValue;
            opMap.borderColor = 'rgb(215, 215, 215)';
        }
    }
})​

5. Add the filters you need including any date or time filter. The script will show a secondary value only when a date filter is on. In other cases, the secondary value will be hidden. 

The example Sample Retail dashboard is attached. Please feel free to implement any additional logic and share your solutions with us!

Disclaimer: Please note that this blog post contains one possible custom workaround solution for users with similar use cases. We cannot guarantee that the custom code solution described in this post will work in every scenario or with every Sisense software version. As such, we strongly advise users to test solutions in their environment prior to deploying them to ensure that the solutions proffered function as desired in their environment. For the avoidance of doubt, the content of this blog post is provided to you “as-is” and without warranty of any kind, express, implied, or otherwise, including without limitation any warranty of security and or fitness for a particular purpose. The workaround solution described in this post incorporates custom coding, which is outside the Sisense product development environment and is, therefore, not covered by Sisense warranty and support services.