Unexpected Behavior When Trying to Share a Dashboard
Unexpected Behavior When Trying to Share a Dashboard Sometimes you can face unexpected behaviors of the system when a dashboard is rendering data,l but you as owner are not able to republish it with other users. Case #1 If this dashboard was imported from another environment please point it to different Data Model and then re-point to the original one back. Check the behavior then. If you still face the same issue please capture .har file during reproduction, and open a new case for support with the relevant screenshots and recorded .har file. Case #2 In case you are trying to share a dashboard, but the list of users/groups is not loading please make sure that: Limit Users Sharing option is disabled in the system configuration: 2. LimitSharesAutocomplete Plugin is disabled (in some cases it has to be even deleted): If you still face this issue, please open a new case to Support and provide detailed description as well as screenshot of current configuration and recorded .har file. Case #3 When the dashboard is published, Sisense returns an error 500. There can be several reasons why the dashboard cannot be republished. Try to duplicate the dashboard. If duplication also returns an error 500, it means that there is an issue with creating a proxy instance of the dashboard/widget. In this case, export the dashboard as *.dash file and open it in any text editor. Using the text editor, find the object's keys, which start with "." and remove found keys: After removing keys with dots, save the modified file, import it to Sisense with overwriting, and republish it. In this article, we have considered 3 cases users can face while trying to share a dashboard.Having difficulty with Dashboard performance
Struggling with slow-loading dashboards? Optimize performance by reducing widget count to 6-8 per dashboard, utilizing plugins like Jump to Dashboard and Switchable Dimensions, and minimizing data load through filters and pre-aggregation. Avoid heavy pivot tables and complex graph functions, and streamline data models by joining on integers and applying data security in a single location. For detailed guidance, check out our performance troubleshooting and optimization resources.Analyze SQL Query vs Visualize JAQL
Answer to the question: What is the "Analyze SQL Query" section of the widget for? I can see its SQL however there are no recommendations or visualizations to show the execution or how to improve the query. There used to be a visualizer for the JAQL but that seems to be removed. Does anyone know if it is being replaced?
Troubleshooting the issue with incorrect Pivot Layout for Expand Pivot On Dashboard PDF
The reason we have created this guide would be to increase the awareness of our customers on how to properly extend multiple pivot widgets for Expand Pivot On Dashboard PDF to ensure you are doing it properly to avoid potential issues with use cases when you have a couple of Pivot Tables on the same dashboard and some Pivots are extended as expected and some have broken layout. Let’s take as a use case the example of the Sisense dashboard with 4 different Pivot Tables, example below:Solutions to commonly found issues when setting up a new Sisense ComposeSDK project during beta
Solutions to commonly found issues when setting up a new Sisense ComposeSDK project during beta The first two solutions involve issues with installing ComposeSDK dependencies during the beta period while the ComposeSDK dependencies are hosted on GitHub, and GitHub is the preferred method for access. When ComposeSDK exits the beta period, the dependencies will be available on other sources that will not require a custom authentication token. Problem - Errors when installing Compose SDK dependencies from GitHub Solution - Make sure a GitHub token is active in your environment configuration, and that your GitHub account is fully active and accessible. If a custom GitHub token is used, ensure the custom token has "Read Repository" permission. Alternatively, you can use a standard full-access GitHub token. Make certain the entire token is included when copied into the terminal. Problem - SSL errors when downloading ComposeSDK dependencies from GitHub Solution - When downloading from a VPN network, you may experience this error. You can resolve this by making the following npm config change with this command: npm config set strict-ssl false In Yarn, the equivalent command is: yarn config set "strict-ssl" false -g Problem - CORS errors in the browser console when connecting to a Sisense server with ComposeSDK Solution - Add the hosting domain to the Admin > Security Settings page. Also, make sure CORS is enabled. A common issue is a trailing slash at the end of the URL when copied from the URL directly; these must be removed when setting CORS exemptions. Include the first part of a domain (the subdomain, such as subdomain.domain.com) as well as the port number if included. Anything in the URL after the first slash is not required and is not part of the domain. Problem - Sisense authentication errors when connecting to a Sisense server with ComposeSDK Solution - Do not include "Bearer" at the beginning of the token parameter; this is not required in ComposeSDK and is added automatically by ComposeSDK. When "Bearer" is present explicitly, it will be repeated twice in the header. Make sure the entire token is copied and test the token using a program such as Postman or Curl and any documented Sisense API if you are unsure if the token is valid.
