Purpose/Benefits This plugin adds additional functionality on how one can display  duration  and  date/time  stamps in a Sisense indicator. Seconds to Duration  takes the calculated integer and converts it to duration in hours, minutes, seconds, etc.               Use Case : Say we are connecting to Salesforce, looking at leads, and wanting to display how long it took between the created date and the last modified date in time. This will allow you to display value in seconds as time(HH:MM, HH:MM.SS, etc). Integer to date  converts a datetime integer value in the EC to display date and time in various formats. (can apply min/max formula to the integer)                Use Case:  I have a dashboard to analyze website performance and would like to display in an indicator the last value analyzed. The plugin would allow me to display the max time(latest value) in my desired date format (March 30 2017 3:03 PM) 1- Install Plugin Download the attachment and unzip the contents into your C:\Program Files\Sisense\PrismWeb\plugins\ folder.  If you are using version 7.2 and higher unzip the contents into your  C:\Program Files\Sisense\app\plugins\  folder.  2- Prepare Data Seconds to Duration:  The formatting function will support any integer value.  It could be a sum of seconds or Seconds difference between two date/time stamps. Integer to date:  In the elasticube convert the Date/Time stamp to an integer date/time value.  Please use the below function. 10000000000 * getyear([Date]) + 100000000 * getmonth([Date]) + getday([Date]) * 1000000 + gethour([Date]) * 10000 + getminute([Date]) * 100 + getsecond([Date]) 3- Choose format Create an indicator For  Seconds to Duration  calculate the seconds you would like to display with a formula   In options menu select desired Format from the integer to date group.   In options menu select desired Format from the seconds to duration group.   For  Integer to date  apply min or max to the Integer as your formula.   In options menu select desired Format from the integer to date group. References/Notes Many thanks to Aryeh, Tak and Ronen for the support in putting this together.

This article will explain how to convert seconds into date-time format on a pivot table. 1. Ensure your seconds column is of type integer. 2. In the widget editor, add the widget script below. Information on how to add a widget script here:  https://sisense.dev/guides/customJs/extensions/#dashboard-and-widget-javascript-extensions     var dateColumns = [4,5,6,7,8]; //select the time columns that should be transformed var thousand_separator = ',' //replace , with your local thousands separator if needed var time_separator = ':' //replace : with your local time separator if needed var returnedData = ""; for (var i = 0; i < dateColumns.length; i++) { returnedData += "td:nth-child(" + dateColumns[i] + ") div"; if (i < dateColumns.length - 1) returnedData += ","; } widget.on('ready', function(se, ev){ var e = element; var w = widget; var d = dashboard; _.each($(returnedData , e).not('.wrapper, .p-head-content'), function(cell){ var num = parseFloat($(cell).text().split(thousand_separator).join('')); var sign = num < 0 ? "-" : ""; num = Math.abs(num); // console.log('num') console.log(num) if(isNaN(num)){ return; } else{ var hours = (parseInt( num / 3600 )); console.log('hours') console.log(hours) var minutes = parseInt( (num - (hours * 3600)) / 60 ); console.log('minutes') console.log(minutes) var seconds = num - (hours * 3600) - (minutes * 60) ; console.log('seconds') console.log(seconds) var hoursText = hours < 10 ? "0" + hours : hours; var minutesText = minutes < 10 ? "0" + minutes : minutes; var secondsText = seconds < 10 ? "0" + seconds : seconds; $(cell).text( sign + hoursText + time_separator + minutesText + time_separator + secondsText); } }) })   3. Adjust the dateColumns array (line 1) with the index of columns you would like to convert. 4. Save the script. Refresh the widget and click apply. You're all set! Before and after the widget script is applied: Notes: the script may reset the values in the second column to 00:00:00, if this happens simply refresh.

Introduction: After a Windows server reboot, the Sisense.CLRConnectorsContainer service fails to start (Windows Event 7000 / 7006), so its connectors (e.g. Microsoft SQL Server) stop working — causing build failures, Live dashboard errors, and connectors missing when adding tables. This guide resolves it by extending ServicesPipeTimeout. Applies to Sisense on Windows (on-prem), all versions. Step-by-Step Guide: Customers usually notice this issue through one or more of the following symptoms after a server reboot: ElastiCube builds fail on cubes that use a CLR-hosted connector. Dashboards using Live data models return errors, because live queries cannot reach the connector. When adding a new table to a data model, the connector does not appear in the list and cannot be selected. The root cause is that the Sisense.CLRConnectorsContainer service failed to start during server startup. In the Windows Event Viewer (Windows Logs → System), you will find events such as: Event ID 7000 — "The Sisense.CLRConnectorsContainer service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Event ID 7006 — "A timeout was reached (30000 milliseconds) while waiting for the Sisense.CLRConnectorsContainer service to connect." The Windows Service Control Manager (SCM) requires each service to respond within a default window of 30 seconds (30000 ms), controlled by the registry value ServicesPipeTimeout . After a reboot, all services start at once and compete for CPU and disk I/O; combined with the CLR container initializing many connectors, the default window is often exceeded, the service times out, and its connectors become unavailable. Resolution — extend the SCM service start timeout This value applies server-wide (to all services). Caution : Editing the registry affects the entire system. Back up the target key first and, where possible, perform the change during a maintenance window. Administrator privileges are required. Log on to the server with administrator privileges. Launch regedit (Registry Editor) as administrator. Navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control (registry path) Check whether a DWORD value named ServicesPipeTimeout exists in the right pane. If it does not exist, right-click the empty area → New → DWORD (32-bit) Value, and name it ServicesPipeTimeout. Double-click ServicesPipeTimeout to open it. Set the Base to Decimal . Enter the extended timeout in milliseconds. Recommended: 180000 (180 seconds). For environments with longer startup times, increase up to 300000 (300 seconds). Click OK to save. Restart the server to apply the change ( the SCM reads ServicesPipeTimeout only after a reboot ). After the restart, confirm that Sisense.CLRConnectorsContainer starts successfully and that Event 7000 / 7006 no longer recur. Optional — mitigate via startup order (can be combined) If services contend during a simultaneous startup after a reboot, set non-core services to Automatic (Delayed Start) so foundational services (Mongo, Zookeeper, RabbitMQ) start first, reducing the chance of a timeout. This works well combined with extending ServicesPipeTimeout. Conclusion: The Sisense.CLRConnectorsContainer failing to start after a reboot is caused by the Windows SCM default 30-second start timeout being exceeded under startup contention. Increasing the ServicesPipeTimeout registry value (e.g. to 180000 ms) and rebooting gives the service enough time to initialize, keeping its connectors available and preventing build failures, Live dashboard errors, and missing connectors. Setting non-core services to delayed start further reduces the risk. References/Related Content  Microsoft — A slow service does not start due to time-out error in Windows . Disclaimer : This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.

Introduction This article outlines the Sisense Favorites Plugin, a client-side plugin that allows users to “star” a dashboard in the “Analytics” home page, this allows users to quickly access frequently used dashboards and makes it easier to find dashboards in instances that could have hundreds of dashboards. Step-by-Step Guide Prerequisites A running instance of Sisense (Linux). Administrator access to the Sisense administration interfaface. Installation Place the “sisense-favorites” folder under File Manager -> plugins. File Manager is located under Admin -> App Configuration -> File Management. If File Manager is not available, enable it under Admin -> App Configuration -> Feature Management -> File Management. Confirm the plugin is enabled under Admin -> Add-ons.  Navigate to “Analytics” page from the top menu Using the Favorites plugin In the analytics page, you can mark a dashboard as a favorite by clicking on the dashboard star, you could do it from the sidebar clicking on either the star or in the 3-dot menu. You can also use the star in the card.  Examples shown below: Download The plugin is available to download here Disclaimer This post describes a custom solution for a specific use case. It may not work in all environments or Sisense versions, so we strongly recommend testing it before deploying to production. This plugin is not officially supported, maintained, or validated as part of Sisense releases. If you have questions or need assistance, please leave a comment on this post. Latest Version that the plugin was tested on : 2026.3.0 Oldest Version that the plugin was tested on : L2025.2.0.510

Automatically Change Widget Title Based on Filter (Linux) Introduction Users might want to dynamically update widget titles based on active filter values for enhanced contextual relevance in dashboards. This article provides a step-by-step guide to implement this functionality using custom scripting. [ ALT Text: Line graph comparing medical treatment usage over years. Treatments like bypass and chemotherapy are tracked from 2011 to 2013, showing varied trends.] Step-by-Step Guide Navigate to the specific widget you want to modify on your Sisense dashboard. Open the widget's settings and locate the script editor. Insert the following script into the widget script editor: widget.on("render", function () { let title = "name(s) selected"; // Find the "Name" filter let filterUsed = dashboard.filters.$$items.find( (filter) => filter.jaql.title === "Name" ); // Get selected Name values or set default "No" text let filterText = filterUsed && filterUsed.jaql.filter.members?.length ? filterUsed.jaql.filter.members.join(", ") : "No"; let isModified = false; if (!isModified) { widget.title = filterText + ' ' + title; isModified = true; } }); 4.  Adjust the column name under "Name" and any default text as necessary to fit your specific use case and data structure. 5. After adding the script, refresh the dashboard. 6. Validate that the widget title changes dynamically based on the current filter selection. 7. Ensure the column name in the script matches the actual filter setup. 8. Confirm that the script editor is appropriately saved and applied to the widget.   Conclusion By following the steps outlined above, you can efficiently update widget titles to reflect filter changes, improving data navigation and user engagement on your Sisense dashboards. While this feature isn't supported natively, custom scripting provides a viable workaround for dynamic title adjustments. Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this please let us know.