Resolving resize widget Issue when the Tabber Widget is in use
Resolving the resize widget Issue when the Tabber Widget is in use Introduction When using the Tabber widget, you may encounter issues where other widgets cannot be resized. This guide provides a step-by-step solution to resolve the problem by temporarily removing and recreating the Tabber widget while ensuring all widgets remain functional. Step-by-Step Guide Identify the Problem: Confirm that the issue is with the Tabber widget not allowing the resizing of other widgets on the dashboard. Delete the Tabber Widget: Before deleting the Tabber widget, copy any scripts associated with it. Remove the Tabber widget from the dashboard. Resize the Widgets: Resize the other widgets on the dashboard as needed. Ensure that the widgets are properly sized before re-adding the Tabber widget. Recreate the Tabber Widget: Add the Tabber widget back to the dashboard. Paste the previously copied script into the new Tabber widget. Verify the Solution: Check if the resizing issue is resolved in the duplicated dashboard. Ensure that the Tabber widget and other widgets are functioning correctly. Troubleshooting Tips Edit Mode Issues: If you cannot change the size of widgets in edit mode, try adding another widget next to the one you want to resize. This can sometimes resolve resizing issues. Conclusion By following the steps, you can restore full resizing functionality. If issues persist, try adding another widget nearby as a workaround. This ensures a smooth and flexible dashboard layout.Tabber - Troubleshooting The Most Common Issues
Tabber - Troubleshooting The Most Common Issues Introduction This article provides troubleshooting steps for the most common issues with the Tabber add-on. Search for the relevant symptom and review the solution that might help resolve the issue. Step-by-Step Guide Symptom: The Tabber widget is not displayed in the list of widget types. Solution: This issue could be related to plugin build problems. Please follow the steps outlined in this troubleshooting guide: Resolving Plugin Build Issues. Symptom: A dashboard with many widgets under Tabber loads slowly. Solution: Loading a dashboard with Tabber loads all widgets, even if they are not displayed under a specific tab. Move some widgets to a separate dashboard and consider using the JumpToDashboard add-on. Refer to the guide on how to use the JTD plugin: JumpToDashboard Plugin - How to Use and Customize. If this does not resolve the issue, please refer to the Troubleshooting Performance Issues guide. Symptom: A custom script used to customize widget functionality with the add-on stopped working after an upgrade, or a widget with Tabber is malfunctioning. Possible symptoms of such an issue include incorrect UI behavior when navigating between tabs, wrong highlighting of the tabs, or widget resizing issues. Solution: Remove the custom script from the widget to verify if the native Tabber functionality works correctly. If it does, the issue is caused by the custom script, which should be reviewed by its developer. Symptom: Tabber script configurations stopped working after an upgrade. The UI of the Tabber add-on is different from the previous version. Solution: Starting from Tabber version 1.2.0 (included in Sisense version L2024.2 and later), configuration parameters supported in the UI are ignored in the script. However, the widget script functionality remains available (as with other widgets), and script code unrelated to Tabber configurations will still execute. If you encounter issues with widget display after updating to Tabber version 1.2.0 or newer, you can revert to configuring the widget via script by adding the following parameter: widget.scriptConfig = true; To return to using UI configuration, change the property to false. Please refer to the Tabber guide for more details. Conclusion The Tabber add-on is a versatile tool for managing and organizing widgets in Sisense. While it is designed for reliability, certain scenarios may require troubleshooting to maintain optimal functionality. This guide provides clear solutions to common issues, helping you address them effectively. For additional support, consult Sisense community resources or reach out to the Sisense support team.How to resolve browser freezing issues (page unresponsive) on your dashboards
This article addresses the issue of web pages freezing and becoming unresponsive when users interact with certain Sisense dashboards. It typically occurs when applying filters or interacting with heavy widgets, which can significantly impact the usability of critical dashboards. The error says "Page Unresponsive":Missing dashboard header and toolbar in a JumpToDashboard dashboard opened on the same page
Resolving missing dashboard header and toolbar in drill dashboard opened on the same page in iFrame (JumpToDashboard) Summary This article addresses an issue where the header and toolbar of a dashboard are not visible when using the "Jump to Dashboard" add-on using iFrames. This issue only happened when opening the drill dashboard on the same page (drilledDashboardDisplayType:3). To resolve the issue, a new type for the "drilledDashboardDisplayType" parameter was introduced starting from V1.5.14 of the JumpToDashboard add-on. Step-by-Step Instructions to Resolve the Issue Update the Script: Sisense has released a fix in version 1.5.14 of the JumpToDashboard plugin. Update your script to use the new display type. For example, prism.jumpToDashboard(widget, { displayDashboardsPane:false, drilledDashboardDisplayType:4 }); Testing the Fix: Ensure that the updated plugin is installed on your development environment. Then test the updated script to confirm that the header and toolbar are now visible in iFrame (by adding ?embed=true to the URL). By following these steps, you should be able to resolve the issue of the missing dashboard header and toolbar when using the Jump to Dashboard add-on in iFrame. Check out this related content: Academy Course Sisense DocumentationResolving Quest Service Fluctuations in Sisense on Windows
This article could help you fix the Quest service issue in Sisense fluctuating between active (green) and inactive (red) states under the https://yourhost/app/status page. The issue usually occurs because of the Sisense.Quest service malfunction.
