We have tried increasing the row limit for CSV download of live models to 250K rows but Report Manager is still limiting output to 5,000 rows which is the query setting of live models. We would appreciate a specific setting for Report Manager that determines the number of rows or have RM use the row limit defined for the report type (in this case CSV and 250K rows). Changing the query limit for the model does impact the report manager, but this impacts all users and every UI interaction, so the data retrieval volume explodes. There should be an independent setting related to report generation. ... View more

Hi, for this moment we have such a behaviour: sum(NULL * 10) = NULL but SUM(NULL * [id]) = [id] in the same time if [id] have values (1,NULL) and we will do SUM([id]) = NULL Is it possible to add some toggle in the system how to work with NULL values. For example, if it is disabled it works as NULL is empty and SUM(NULL * [id]) = [id] But if it is enabled, so all NULL should be works as in mathematic SUM(NULL * [id]) = NULL etc ... View more

Summary: Live Model slow, can be fixed by prioritising a filter I use a Live Model to return info about a few records from a big dataset. One filter should efficiently narrow the big dataset down. But the server sometimes applies other filters or joins first, making it unusably slow. I want an option to tell the Live Model to fetch the important filter's items first, and then write those items into the filtering clause when writing the main query. That will cause the server to correctly discover that applying the important filter first is the most efficient query plan.   Details (I'm querying SQL Server, but I suspect other sources would also benefit.) Sisense documentation says "Analytical Engine inserts filtering clauses into the innermost SQL statement. This means that filtering is the first operation performed". Sometimes that helps performance. But it depends on the source server. If you apply multiple filters or joins, the server may decide to perform a less efficient one first, or it may parallelise. In my case, my query went from a few seconds to over an hour depending on the server's choice.  The problem is that the server can't estimate the cardinality of the "filtering clauses" entered by Sisense. For example: The server doesn't know that my "dimCustomer.[Customer Name] = 'Joe Bloggs'" filter returns only 100 rows from my fact table, whereas "dimDateTime.FiscalYear = 2022" returns 100,000,000 rows from the fact table. There is a solution. Instead of "Where Fact.[Customer ID] In (Select [Customer ID] From dimCustomer Where [Customer Name] = 'Joe Bloggs')", Sisense should first run the query Select [Customer ID]... query to find that Joe's ID is 5. Then put the result into the filtering clause, i.e. "Where Fact.[Customer ID] IN (5)". For a hardcoded ID like that, the server can estimate the cardinality, so it sees that filtering on [Customer ID] first will be more efficient that other query plans. Sisense mustn't just do that for all filters. If it tries prefetching "dimDateTime.FiscalYear = 2022", that'll return all 31,536,000 seconds, and then pass that back in the query as "Where Fact.DateTimeID IN (...)".  Solution: The solution I request is: Allow the Live Model developer to set a "Prefetch Filter Items" flag on a field. If it is set, when a widget or dashboard filters that field, then Sisense first creates a query "Select dimSomething.[Relationship column] From dimSomething.FieldWithPrioritisedFilter". Then, when building the main query, change the "filtering clauses" to be "Where Fact.[Relationship column] IN (<put prefetched values here>)". Reference: For reference: https://docs.sisense.com/main/SisenseLinux/analytical-engine-overview.htm: Analytical Engine inserts filtering clauses into the innermost SQL statement. This means that filtering is the first operation performed, minimizing the number of rows that need to be scanned in order to process the query. Complex filters, such as top ranking and filter on measure are significantly improved as a result. Proof of concept: Build a Live Model. FactA joins to DimB on ID_B and to DimC on ID_C. The source is SQL Server. In SQL Server, all three tables have millions of rows, and the FactA has foreign keys to DimB and DimC. DimB.Name has a unique name for each row. DimC.Type is 1 for half the rows, and 0 for half the rows. Create a widget that filters for DimB.Name=<some name> and DimC.Type=1. Use SQL Profiler to find the query your Live Model runs. Run the query; it should take over a minute or time out. Then change the "Where FactA.ID_B IN (Select ID_B From DimB Where DimB.Name IN ('<some name>'))" to instead be "Where FactA.ID_B IN (<copy paste the ID of <some name> here>)". It should run much quicker. The original query might run quickly without change, depending on server settings; if so, mess about with more complicated joins or ask me. In my setting key queries were reliably slow. ... View more

Sisense charts show tooltips when you move the mouse above them. When showing those tooltips the website automatically formats numbers in the tooltip in order to simplify the reading and shrinks those numbers if they go above 10k. Most of the times this is what I want as a user, but not always. According to my observations, tooltips stop showing the real number and show a simplification when it goes above 10,000  (e.g instead of showing 16742 it will show 16.7k). This idea would be to allow this number to be displayed in full instead of the shrinked version. Sometimes it is just useful to see the real value and not the simplified one. As a user, I'd like to see the real one sometimes. There are two possible ways of implementing this that come to mind, in the Tooltip section when editing a graph: Add a checkbox, clickable, with the current behaviour by default "[ ] Show raw numbers". This would be below "[ ] Show Total in tooltip" Add a threshold numeric input so that users could manually specify from which number onwards the formatting would shrink (e.g 10,000 by default).  "Shrink numbers above: [            10000]" First option is simpler to understand, second one is more flexible.  Right now, the workaround I'm using is to Edit a chart, then click on "Output" in order to see the real numbers as a table, but this is inconvenient. Here is an example of the number I'm referring to, in a chart. You see 15.9k and I'd like to see 15935.   ... View more

When connecting a notebook to an Elasticube, there is no indication what subset of SQL is expected to work Simple features like setting Cell 1 = select * from some_table Cell 2 = select * from Cell1 give errors suggesting the WITH syntax is not permitted, which is a bit of an issue given how heavily notebooks rely on it. There also seems to be limitations using ORDER/LIMIT in subqueries (which is fairly essential if CTEs arent allowed) Any real use of Notebooks on Elasticubes seems quite far away without finishing this feature ... View more

Use Case: As a user, I want to be able to share a dashboard with another user with the pre-selected filters so that they can see the same results as I do. Description: The current functionality of the dashboard filters is user-specific, meaning that each user has their own selected filters. However, there is a need to enable users to share a dashboard with another user, ensuring that the pre-selected filters are applied, allowing them to view the same results. This enhancement would allow a user to easily share a dashboard, including their filter selections, with another user. When the recipient accesses the shared dashboard, they would see the same filter settings as the original user, providing a consistent and synchronized view of the data. By enabling the ability to share dashboards with pre-selected filters, users can streamline collaboration, discussions, and decision-making processes. This feature enhances the dashboard-sharing experience and ensures that all parties involved are viewing the same data and insights. ... View more

I use pulse alerts to alert my clients when there is data on Sisense that needs their attention. The Pulse alert emails are accompanied by a big yellow 'Open Pulse' button. This button is the obvious thing to click on, but unhelpfully, it leads to the 'Pulses' tab of Sisense, not the actual dashboard. As a viewer, I want to jump straight to the dashboard, not be confused but this 'Pulses' tab which I most likely will not have seen before nor used. An option to have the button instead open the dashboard directly would be much better and make it much easier to engage customers with the Sisense platform.   I know there is a link to the dashboard on the pulse itself, but going via this screen this is inconvenient at best and confusing at worst. ... View more

We embed and white label Sisense and our premium customers have the ability to author new dashboards with the formulas and attributes we provide. Our users want the ability to create new attributes, comparable to creating a new formulas. Examples: new "Northeast Location" attribute = existing location attribute that we provide where sites = A, B, C new "Shutdown 2023" = existing date field that we provide where date range between X and Y Concatenation of multiple fields to form a new attributes, comparable to Excel new "Is True" type attributes = existing attributes we expose if value(s) = ... Customers want the ability to create their own custom attribute, have then be added to the default values list, in their own "custom" section, where they can search and reuse their own creations. We are a multi-tenant solution provider so tenancy of these custom creation must stay "in tenant" and must do so with us implementing the multi-tenancy feature of Sisense (as we are already deployed and this is not yet robust enough for us to utilize) ... View more

A nice feature in Microsoft SQL Server is the ability to see multiple data sets from queries in stacked windows. Currently only one query can be executed at a time and only display that one query's data set. It would be nice to be able to compare data by having multiple data sets appear at the bottom. Currently I have to open multiple browser windows to compare values and it can get a bit busy. It would be nice to compare 2 or more queries in the same window. Select * from table 1 where id = 123 Select * from table 1 where id = 456 data set for id = 123 data set for id = 456 ... View more

With the "Jump to Dashboard" add-on installed & the "suppress _drill_" dashboard parameter configured, SiSense hides the _drill_ dashboards from everyone except the owner (which includes the sisenseadmin account).   As a result, it is hard for the administrator to view and/or manage _drill_ dashboards that are owned by a designer.   There is a workaround via F12 that SiSense showed me, but it's not intuitive.   It would be nice if there was a parameter to allow the sisenseadmin to always have the ability to see/edit the _drill_ dashboards (or perhaps that should be the default behavior). ... View more

Currently, when you share a dashboard you can have it email the dashboard out to people following a couple different schedules: Every Elasticube update (with a limit on times per day) Daily (can specify which days and a time) Monthly (can specify which months and what day of the month) The trick is that elasticube updates includes failed updates.  I would like to add an option to exclude failed builds from triggering these dashboard update deliveries. Now that we have alerting for build failures, there doesn't seem to be a reason for dashboards to deliver without new information. ... View more

A user would like to remove the title from the secondary indicator. Unchecking the Title box works for only the primary value. They would like the same functionality for the secondary. ... View more

As of L2023.3, in Sisense’s Helm Charts , “Tolerations” are supported by the micro-services. It prevents end-users from configuring “Taints” on the node that they want to dedicate to Sisense. Since no “Taints” are configured, so all nodes can become eligible to host Sisenses’s pods. They experienced that scenario when pods from some other application services were scheduled on a Sisense node. Would you please consider allowing the pods to be protected not only with  “Toleration” but also with “Taints”. The justification for this is that, even though it is mentioned in prerequisites documents that Sisense should be installed on dedicated servers, there is a non-negligible factor from the customers perspective that is the overhead administrative costs, especially for customers who must already manage numerous clusters for several applications, multiple environments, and redundancy.   ... View more

There are cases where the Sisense queries have to read from views. Would you consider allowing to issue queries like “ALTER database.materializedView REBUILD”  instead of only allowing select commands, in this case this would allow to refresh data that would be selected by the jdbc connector. ... View more

Hello, Currently, we can only sort reports based on column "Report name". It would be good to sort reports based on "last run" column too. It would also be good to have sizeable column headers for better readability. Thank you ! Franck ... View more

Currently the box and whisker plot is not supported when using a live model. When the widget is created, it has an error and won't show any data. We would really like that to be supported on the live model. Article showing that its not supported: https://docs.sisense.com/win/SisenseWin/live-connect.htm ... View more

The default color scheme for the sunburst chart is defined per ring, while it should be per category. For example, category 1 has the red color, category 2 has green, and category 3 has blue color scheme ... View more

A while back the JTD didn't pick up measured values properly and we configured our dashboards so that the measured value filters were not relevant to the jump. We have some situations where there are conflicting filters with-in the measure (e.g. comparing different things as a numerator and denominator). Can you add a widget config option to ignore measured value filters? It would require adding an item in config and then adding an if statement to the filtersHelperService.js in the getMeasuredValueFilters like if(config.ignoreMeasureFilter) return [] ; around line 560. This would greatly help us out as we do have fairly complex filters running and much more often than not want to only consider dashboard and widget filters in the Jump. ... View more