CORP Support for iFrame Embedding
A customer has Sisense embedded in our web application as an iframe, and we are having some issues related to Cross-Origin Resource Policy. We know that Sisense has CORS settings, but we have not found anything related to Cross-Origin Resource Policy (CORP) headers, like cross-origin-embedder-policy or cross-origin-resource-policy setup. The customer would like the same configurations and settings at their disposal
Dynamic link generation based on values in table/pivot cells in ComposeSDK
In Compose SDK, it would be a great idea to create a unique format for crafting links from the content in table/pivot cells. Upon detecting this format, the text would be automatically transformed into a link with the full URL being crafted from the contents in the cell itself, which should have a format like <hostname>:<port number>/<additional_parameter1>/<additional_parameter2> and so on. Of course, they would be fully customizable, and the trigger for the transformation should be some kind of reserved character at the beginning or end of the cell's content. The advantages of such a solution would be that since the data for these cells is taken from the database, the values there could be freely used across any range that is desirable for the designer. These links should also work when the widget is embedded, of course.
scripts and plugins working with ComposeSDK
To ease the transition between dashboards embedded via iFrame and the ComposeSDK, widget scripts, dashboard scripts and (most important!) plugins/add-ons should also work with ComposeSDK, e.g. via a flag "allow_scripts_and_plugins" or similar. That way, when moving between the 2 embedding methods, there is less friction.Add indicator for downloading a widget
While downloading a large csv/excel file (over several hundreds mb file) from the widget, there would be a long delay of couple minutes before the browser indicates the file has been downloaded. During this time, the user has no indication if the request to download is in process or has failed. It would be good to have an indicator to show the download of the file is in progress, so user would not click the download multiple times thus causing multiple queries to hit the backend.
Building Confidence (and BloX Widgets) with the Help of Sisense Trainers
My personal experience taking two interactive training sessions with Sisense trainers as a new Sisense user. How I’ve been able to apply new skills to my dashboard work and feel more confident in dashboard design and customizing Blox widgets to get exactly the look and feel I want for my customer experience.
Responsive pivot table widths
Pivot tables are currently not responsive and it doesn't take up the full width of the available screen in an embedded dashboard. For table widgets, we can set the width to "auto" which uses the whole screen space. Similar functionality can be added to pivot tables to make the dashboards look more formal and appealing.
How to prevent iframe reload when switching tabs in React app embedding Sisense dashboard?
Hi everyone, I'm embedding a Sisense dashboard using an iframe inside a React-based platform. The iframe is rendered on a dedicated Insights tab route: insights. Every time I switch away from this tab and return to it, the iframe reloads, which causes unnecessary load time and loss of dashboard state (like applied filters or selections). My goal is to mount the iframe only once, keep it cached in memory, and just hide/show it based on tab switching, without triggering a reload. Here’s what I’m trying to achieve: Mount the Sisense iframe only once (on first visit to /insights) Persist it in memory even when navigating away Show it again without reloading when coming back Has anyone implemented this pattern or has best practices around iframe caching or persistent embedding of dashboards in a React environment? Would love to hear suggestions or recommended approaches from the community! Thanks!
