We create a basic set of pre-built dashboards that we publish, where business users can view but not modify.  We also have two-tiers of analytics offering for business users (standard and premium).  On our common, pre-built dashboards, which are available to both standard and premium, we would like the ability to expose Simply Ask to only those users of premium (hiding it from those who are standard).   While this may be achievable via a 2-model, 2-dashbaord set approach, we desire to manage a single set of dashbaords and model to simplify deployment overhead and maintenance. ... View more

  Background and customer pain points Currently Sisense is capable of showing numeric figures in abbreviated format, but only in the American/European short scale form: thousand (k), million (M), billion (B), trillion (T). In east Asian countries, there is a different scale form, so viewing information in these k/M/B/T is very difficult to understand.  Non-abbreviated Standard abbreviation (US/Europe) Indian abbreviation East Asian abbreviation 1,000 1 k (thousand) 1,000 1 千 10,000 10 k 10,000 1 万 100,000 100 k 1 lakh 10 万 1,000,000 1 M (Million) 10 lakh 100 万 10,000,000 10 M 1 crore 1000 万 100,000,000 100 M 10 crore 1 億 1,000,000,000 1 B (Billion) 1 arab 10 億 10,000,000,000 10 B 10 arab 100 億 100,000,000,000 100 B 1 kharab 1000 億 1,000,000,000,000 1 T (Trillion) 10 kharab 1 兆 Business case description/value To be able to select the scale form for number abbreviations for different APAC regions as well. Use case A user in Europe is creating a dashboard in Insights with an indicator to show total profit in an Indicator form. Let's suppose that the total profit to display is 1,610,000. 2. Europe user formats the content to abbreviate the display in the short scale form. User will see "1.61 M". 3. A user in Japan is creating the exact same dashboard on the same data. 4. Japan user formats the content to abbreviate the display in Asian scale form. User will see "161 万". 5. A user in India is creating the exact same dashboard on the same data. 6. India user formats the content to abbreviate the display in the India scale form. User will see "16.1 Lakh".   ... View more

It would be better to have more control options over exactly when the email report for a dashboard is triggered out to users. Currently we use the option "Every Elasticube update. No more than 1 emails per day" but that has issues: 1) We would only like the email to send if the Elasticube update is successful, rather than every update (including build failures). Otherwise we send a report out with missing data. 2) The rule of "No more than 1 emails per day" doesn't seem to be working properly. Meaning if we refresh the Elasticube more than once per day, users are receiving duplicate reports. ... View more

Selecting a value in a row selects only the value and not the row. This prevents passing a specific value unless the unique value is exposed in the table and selected by the user. Right clicking on a value in a row should provide the option to select the specific value that was clicked on, or the specific Row that the value is in. For instance: A pivot table of people with lots of names and dates. If a user finds the person they want to drill into they can drill into the name, but there might be duplicate names, so the drill through will have all the people with the same name. If they select the birthdate of the record it will drill into that birthdate, not specific person with that birthdate. A third unique value has to displayed for each result, like a userID. This value has no meaning for the end user, other than they have to click on the userID and only the userID if they want to drill into that user. There should be a way to select the row, not just a specific value. ... View more

There should be an Embed SDK function that sets all editable Widget or Dashboards filters to Empty/“Include All”. Right now we have to either remove the filters completely and re-add them, or set each filter individually. It would be nice to be able to set them all at once. ... View more

Currently Notebooks provide a powerful opportunity to access and visualize data utilizing SQL and to add these to fusion dashboards.  Fusion's primary analytics environment allows for powerful dashboard-wide filters.   Currently dashboard filters do not apply to charts or tables which are created through notebooks even if the notebook is pointed to the exact same data table and column as other dashboard widgets.   Please develop the ability for dashboard filters to filter both fusion dashboard widgets and also notebook-based widgets.   ... View more

Current Behavior:  When user selects filter options such as Contains, Does not contain, Starts with, Does not start with , End with , Does not end with etc.  , the resulted suggestions can only be viewed , but cannot be filtered.  Proposal Users should be able to select a filter option, enter a value and use the suggestions to filter.  Currently its giving an inconsistent user experience (Some options are filterable such as Is, Is not,  & few others are not) OR, should display an appropriate label to say the least .  I initially considered this as a bug ,and later realized as a product design.  Thanks ... View more

Hello, It is not possible to rename a cube, but it is possible de copy it. If we then move the existing dashoards to the copied cube, we have workaround to rename the cube. But with Perspective it is not possible to rename nor to copy. => It would be useful to be able to copy (duplicate) a perspective. Thank you ! Franck ... View more

Sisense currently supports Shared formulas to be moved as a part of data Models only. However not all Designers have access to edit/view data models So, they can't move shared formulas from one environment to another via data models Shared Formulas should be exported along-with Dashboards also   ... View more

working with the plugin ExtenedPivotOnPDF shows the header of the Pivot only on the first page, doesn’t show starting form the second page. Please add header of table on all the pages. ... 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

Currently, the ArcGIS Map Integration allows only one data point to be displayed as a tooltip. It is crucial for us to have the ability to show multiple data points in the tooltip. Adding support for multiple data points in the Detail field and previewing them as tooltips would significantly enhance the functionality.   Thank you.  ... View more

Windows Sisense currently has no way for us as administrators to control how much ram is being used by elasticubes. From looking at the community site, it appears that linux has a way to do this through data groups, but when consulting with support, I have been told to increase our resources, simplify our models, etc.   The big problems that we have observed at my company is that 1. Sisense seems to take up the resources it is given - when ram is increased, usage percentage stays at the same level 2. If something does go wrong and resources begin to get consumed, there are no guard rails in place to stop whatever incident is happening from taking down the whole server This second case has happened only a few times in the years we have had Sisense, but I don't like that I have no way to be proactive about these issues.  ... View more

I want an option to remove the "Can Design" role when sharing dashboards (yaml? admin settings? does it already exist?). I dislike the role because: Users don't realise that they're editing a temporary copy, and that the owner can Republish to overwrite. They might make many changes, and then months later someone republishes the owner/master version. I'm not entirely sure if republish always overwrites - if the user has made changes, do they keep their version when you republish or get the new one? If they keep theirs, it makes it confusing when trying to make changes requested by a user, because you make a change, click republish, and then the user forgets to click the revert-to-master-button. Instead of the Designer Role, users can just duplicate the dashboard. That way, no risk of overwrite or confusion.   ... View more

We use the SSO JWT option for Single Sign-on. In Single sign-on configuration, we specify the Remote Logout URL. We want a way to specify this remote logout URL at the user group level. ... View more