Hello, In a multitenancy environment, it would be useful to be able to define an email notifications sender per tenant. ie : Tenant "Tenant A" : mail sender is "Sisense - A" Tenant "Tenant B" : mail sender is "Sisense - B" For now, email setup is only available from the default tenant, therefore unique accros all tenants. Thank you. Franck ... View more

We have a few dashboards where the displayed data is only valid when a SINGLE ITEM is selected for a filter. We want to have the standard dashboard filters that our users are used to, but we want to prevent them from selecting more than one item at a time.  In the attached image, we want the red highlighted areas to be disabled (not selectable) for non-owners/non-editors of the dashboard.  We should be able to publish the dashboard with a default value for the filter and allow them to select a different value, but not multiple values.  ... View more

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

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

It would be very helpful to be able to pass User or Group parameters as Claims in a Web Access Token. This will allow customers to leverage the dynamic features related to User/Group Parameters (e.g. dynamic live query) when using Web Access Tokens. ... 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

We would like to configure multiple data security rules on a live data source table. With the available APIs there is a constraint to set one rule at a time. Having an API that accepts a collection of multiple rules is desired for our use case since we have more that 18,000 rules to be set. ... 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

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

Hello, We recently had an AI demo meeting where we were shown some of the AI capabilities of Sisense. However, the LLM providers that are currently being supported do not align with the AWS eco system we are currently using in house. Would it be possible to support AWS Bedrock as an LLM provider? At the moment this is the only road block on our end from trying your LLM supported AI features within Sisense. ... View more

The UI limits the number of recently used drill-in fields to 5. I've attempted to write custom JavaScript to add additional entries to widget.metadata.drillHistory, and verified they are added to the array successfully, however the UI will only show 5 drill-in values. This is important because our customers need to be able to "slice and dice" data visually and the best way to do that on a single chart is by using drill-ins. We do not want customers to have to "Choose another" because nearly all of these customers are viewers and do not have or need extensive knowledge of the data model. Having an option to increase this, either as a dashboard JavaScript override, or as a feature in the configuration of the product itself would be very beneficial. ... View more

The page controls to change the pages are currently within the widget and its functionality is limited: Thus, if the number of rows to be displayed are increased to 50 or so, the widget window would get expanded and user will have to scroll to the bottom of the dashboard to see the page controls or change the widget page.  This can be avoided by placing the page controls at the bottom of the widget window and not limiting it to the size of rows. So the widget window size stays fixed and the user can scroll through the data within the table widget. This also helps view the dashboard in the page  without having the need to scroll down at the bottom of the dashboard. Additionally, also allow the viewer to increase the number of rows to be viewed in the widget. Example, a user should be able to increase the number of rows for a table widget to fixed numbers as 50 or 100. ... View more

I have previously worked with Periscope and found the SQL Snippets tool to be very helpful (https://dtdocs.sisense.com/article/snippets#:~:text=To%20create%20a%20SQL%20snippet,button%20and%20name%20the%20snippet.&text=Snippets%20with%20these%20characters%20included,the%20box%20and%20click%20save.) Now my team use Sisense Fusion and we still have a need for this tool, despite it not being a feature in Fusion. We hope to have it available in the future.  ... View more

Regex is of course supported when querying through the import MySQL query, but custom Sisense tables do not support regular expressions. It would be useful to have regex functionality in custom tables and custom columns as well. ... View more

Current State: As of now Sisense supports adding of pulse alerts only for select chart types, like, Indicator, Area, Line, Bar and Column. Expected State: Sisense shall allow rest of the chart types as well to add pulse alerts. It is observed in other competitive products to be available for all the chart types. Customers like us (Blackline) have many use cases of tabular widgets and end users expect alert to be added to these widget types.  ... View more

Current state - You can only use color conditional formatting on numerics in the value section of a pivot table.  But it would be nice if you could also apply color formatting on text.   An example of this would be green on the value 'Confident', orange on the word 'At Risk' and red on the word 'Not Possible'. This text would be values existing in our database, not something created within Sisense.  ... View more

Add the ability to adjust the BaseTableMaxThreads at the Data Group level. This will allow for "right sizing" memory allocation that is consumed during the build process.  For example, I have low priority elasticubes residing in the default data group. High priority elasticubes reside in a "High Priority" data group with custom settings for "Stop When Idle", RAM, etc. Currently, our environment is configured to load 3 base tables concurrently (BaseTableMaxThreads  = 3). This setting impacts both high and low priority data groups. I want to be able to set my low priority data group to only load one table at a time (BaseTableMaxThreads  = 1) to reduce memory consumption on the server during builds. I want my high priority data group to continue loading 3 tables at a time. The trade off is the default data group will load data slower but will consume less memory/CPU during builds, freeing up resources for the high priority data group. ... View more