Request: Provide a standard way for supporting multi-currency support. Use Case: Enable end users to create widget and dashboards where they can switch between multiple currencies. Background: There are various posts on how to implement multi-currency by adding an exchange rate dimension and using a formula similar to Local Amount = (Amount Field) * (Exchange Rate) and using a filter to select the desired currency (E.g. USD, EUR, GBP). This process works well when you have dashboard designers, but it doesn't work well if you want end users to create their own reports.  If they do things wrong the Amount may be multiplied by the number of currencies supported. They are required to enter a formula instead of simply selecting a field to report. Recommended Solution: Add ability to add Formula fields to the data Model.  The data designer would create a standard field with the formula.  The formula would be evaluated within the dashboard not during cube build.  Note: there are probably other uses cases for data model defined Formulas that are evaluated within the dashboard. Add ability for automatically adding the Currency filter when the data source is used. ... View more

Each time I want to share my dashboard, I click the Share button and make sure the person I want to share the dashboard with has the right permissions, and then I have to copy the url, making sure I covered it in fully. Instead, I suggest to have a "copy link" button in the form, which I can simply click and know that I now have in the clipboard the dashboard's url to share. Another option would be to have a "copy link" button that is revealed when I hover on top of the dashboard's name, to allow easy copying of the shareable link, even without opening the "share" form. ... View more

Sisense maps are running on Mapbox. Mapbox supports localisation, i.e. showing the map objects like countries, cities etc in a chosen language, see https://docs.mapbox.com/help/troubleshooting/change-language/. I would be great if Sisense could support translation of maps by e.g. giving the user's preferred language as localisation parameter to Mapbox. ... View more

We have a use case where a report schedule is supposed to run daily/weekly only during certain months of the year(seasonal reports). This could be done using the time frame section in report manager, however, at the end of the season, we will need to manually update each of the schedule's start and end date, which may not be feasible when there are over 100s of schedules as such. It will be really helpful to be have this ability in the schedules, so schedules can run only certain months in the years. ... 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

To filter any data we need to add the filter on the right panel. Though this is possible only for a desinger and if a viewer wants to filter any other columns in the widget after the result set is displayed, they will need to download the table and filter in csv/excel. It will be really nice to be able to further filter the result set by viewer after the data is processed/displayed by having this option visible on every column header. Currently, clicking the column header only sorts the data, keeping a filter option on every column can allow the user to narrow down the results before downloading the file. Using this option, the viewers can filter any of their columns in table widget without having the need to download and analyze the results outside sisense. ... View more

Unsure if it has to do with the numerous columns that we have in this table specifically but there is no drag scrollbar to be able to see beyond the first 6 columns. It would be nice to enable scrolling despite numerous columns so that users do not have to manually download the report.  ... View more

We are OEM with several hundred client organizations, each of whom have their own set of our standard data models. The data sources are prefixed with a client code so that the same data model can be distinguished and secured between clients. Have two sets of the same data models with different data.  Have two users, each with access to only one of the two sets of data models. One user creates a dashboard that uses multiple data sources. The dashboard is export to .dash file and shared to the other user who imports it. The second user then needs to update the dashboard data sources to see the dashboard render with their data. Importing that dashboard into Windows and updating the data sources: 2DSDashImportWindows.mp4 Just update the data sources at the dashboard level. Importing that dashboard into Linux and updating the data sources: 2DSDashImportLinux.mp4 Update one data source at the dashboard level. Then update each widget in the dashboard to use that data source. Then update the other data source at the dashboard level. Then update each widget in the dashboard to use that data source. How many widgets in your dashboards 😉 ... 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

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.   ... View more

In addition to not being able type in dates with the Calendar item in the date filter (I submitted that as a separate idea to be able to type in dates), the general date selecting user experience is quite cumbersome.  It's hard to write this out and much easier to show.  But the short story is that it is difficult to select the dates on the first try.  A pretty typical interaction with the calendar component goes something like this: Open the filter Select Calendar Pick the start date Perform however many clicks it takes to get to the date you need (sometimes this can take a few clicks if you are going back a few years/months) At this point you think you have selected the start date Now, move your cursor to go select the end date At this point, the start date loses your initial selection.  I think this happens 90% of the time Sometimes the issue is that the start date gets set to the new end date Sometimes it resets before you even get to the start date Sometimes it goes back "Select" like you never picked a date This behavior is quite frustrating.  I have experienced it quite a bit myself and customers have complained.  I hope there is something that can be done to improve it. ... 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

Currently the way the Sisense creates its query for dashboards, is it creates a common table expression for each entity created in the data model. Then applies the date filter after the join between the CTE.  During this process, it looks like its scanning the entire table of the CTE, which can be problematic if the underlying table used in the CTE is really large.  It will be better if the filter for dates can be applied within the CTE for such large tables, thus avoiding large table scans and help load the report faster. Is there a way this can be achieved by altering the design of the data model? or are there any plugins to support it? ... View more

Hi, We have two cloud servers in Sisense: one for development (staging) and one for production. The staging server connects to our staging database. The production server connects to our production database. All cubes and dashboards are identical except for database connection strings and names. Our Git branching strategy follows these steps: Create a feature branch from staging. Make changes and push them to the feature branch. Open a pull request from the feature branch to staging. Test changes in staging. If approved, merge staging into master (production) to deploy changes. The Issue Git integration tracks database connection names, meaning both servers must either run on staging data or production data—this is not feasible for us. Proposed Solution We suggest implementing a decentralized environmental variable for storing database connections. For example: Use {database-server-name} as a placeholder in configurations. Set database-server-name = db_server_staging on staging. Set database-server-name = db_server_production on production. This would allow the same codebase to dynamically connect to the appropriate database without manual adjustments. Would love to hear your thoughts on this! ... View more