Currently, the aggregation function depends on the type of the dimension : - Text or date => Distinct count - Numeric => Sum In our use case, this default assignation is not always accurate as it is sometime required to use Distinct Count with numeric fields. It would be good to hauve the default aggregation function to be choosed by the cube designer, when developping the metadata layer (ElastiCube or Live cube). This way, the dashboard designer will be proposed the accurate function without need to change it. This is particlary interesting with a users population that don't have analytics background and for which choosing the correct agregation function is not obvious. Thank you ... View more

On the Analytics page, there is a menu on the left where dashboards are listed. It is possible to create folders to organize dashboards. Folders can be nested within other folders. Currently, It is not possible to drag and drop one folder into another. This would be useful to have. ... View more

This is for LiveConnect data sources using Snowflake. We cannot filter Datetime columns at the hours level. Either "last n" hours or "between 08:00-12:00" as example. I would like to see this added as a capability of filters. ... View more

Scenario: embedded Sisense By default, when creating a new widget, Sisense puts the user into the widget "Wizard Mode", which then requires the use to click "Advanced Configuration" to view the full-feature widget editor. We don't want our users to use "Wizard Mode" and to always be placed directly into "Advanced Configuration". This should be a configurable setting at the Admin level. ... View more

Because a non-trivial amount of the population is colorblind, it's a best practice to never rely solely on color when indicating behavior or status of a UI element. The filter-pane buttons are by default, I think, green for positive selection, red for exclusion, and grey for unselected. It would be better if there was also a small icon in the button that would indicate checkmark if positive, "X" if negative, and blank if unselected. Or perhaps, if Unselected (red), show a thin "X" over the whole body of the button. Thank you. ... View more

We support multiple applications of data within a model, as there is crossover between the applications; however, our customers have granularity to choose which application data with which they are allowed to see when they create new dashboards. We use column level security for attributes today so that Application A author can only see table of data pertaining to application A while Application B author can only see tables of data pertaining to application B (note that a user can have both author rights and see all both application data). We found that this does not pertain to Shared Formulas.  This now increases the "noise" that authors see, as they are seeing formulas for an application that isn't something they can readily use. ... View more

When you export a datamodel to a .smodel file, the file includes connection information (server name, password, etc.). I would like an option to exclude that information when I click export. The export dialog already offers check boxes for Data Security, Scope Configuration, etc.; this feature could be just another one that says "Connection Information". Ideally, I'd like it to exclude the connection information by default, so users are forced to explicitly ask to include it, which will remind them to consider the file as sensitive. But I understand if you don't want to change default behaviour that other users are used to. When you import a model that has had this information removed, the import should let you to enter new connection information, or leave it as placeholders like Server=0.0.0.0 and password=Password so you can enter the information after importing. Sisense GIT already removes this information; this feature could work in a similar way. You could even deliberately make GIT's "non-tracked entities" all appear on the list of export options. GIT per this page: https://docs.sisense.com/main/SisenseLinux/asset-translation-and-management.htm?tocpath=Git%20Integration%7C_____3#Non-trac ... View more

We want to rotate the API key for our system user but need to make sure there's no downtime.  This means we need to have 2 keys working in parallel for the same user for a period of time until we can cycle all of our services to pick up the latest api key. The problem is as soon as the API key is rotated, the old key immediately stopped working.   Majority of systems out there support key rotation (like allowing a time delay before the old key expires like FB app, or ability to temporary create a second key and then we can promote it as primary once we are ready).   Key rotation is a best practice for security principles. ... View more

Two problems: Datamodels store old connection information without the user being aware. That increases the chance of accidentally exposing credentials to a different security context. Sisense R&D said that the reason is to show Recent Sources. When you change a dataset, you can end up with two copies of the dataset, which is confusing.   Ideas for improvements (take some or all): Sisense could track the Recent Sources separately. Then Sisense could automatically remove empty datasets. Sisense could show empty datasets under Data Sources in the data model editor UI, and give the user a delete button for them. The Data Model editor could have a drag-and-drop to move tables between data sources. When you click export, there could be a checkbox "Remove data source connection information".   More detail about the problems here: https://community.sisense.com/t5/support-portal/bd-p/SupportPortal?page=casedetails&caseId=500Pk00000Es4PyIAJ and here:https://community.sisense.com/t5/help-and-how-to/models-have-empty-datasets/m-p/20632#M222   ... View more

When utilising the Fiscal Year functionality, it is frustrating that there is no option to display the calendar year as a formatting option. We are based in Australia and our Fiscal Year starts in July, so our 2023/2024 Fiscal Year (called 2024) runs from July 2023 to June 2024. If I create a simple pivot with our Date, Year (Calendar Year formula) and Fiscal Year (formula in format YYYY/YYYY), then you can see that the date is actually distorted.  There is no way to display that this date actually falls in 2023, which is the case for the first two records in the below pivot. Applying a filter with a date range handles this correctly, but it is confusing for our Finance department as to what date this is referring to. I've connected with Sisense support and they've provided a solution for a Date Display Field (thanks @AssafHanina) which does solve the issue, but then we need to have complicated rules for dashboard designers to use X field on their Dashboards but Y fields on filters, etc. I feel like an additional date format of "cy" for Calendar Year would solve this issue from the display side and make things much simpler.  Some logic already exists for "yp" for the previous year, this would be very useful for our designers to have this additional option and to keep the date as one field rather than needing a second. Has anyone else encountered this issue or would find this useful? ... View more

When filtering on a numeric field and using a Value type filter, I often want to filter on a dynamic value. As the Ranking type filter can take a formula, I would make good use of a Value type filter that also allowed for a formula. ... View more

When a widget returns no data and is displayed in column format - it would be nice to have an option to show the column headers only to give users a reference point as to what data will be shown. Thanks ... View more

Hello, In a multitenancy environment, it would be useful to be able to define different "look and feel" theme for each tenant. Currently, the one define on the system tenant is applied to every tenant. Thank you. ... View more

---Summary:--- When you drill, create a filter. Link new filter and the drill-breadcrumbs, so if you change one, it changes the other. Make it an optional, per-widget setting. ---Details:--- Sometimes I build a dashboard with a "main" widget for the user to explore, plus a few indicator widgets above it. It'd be nice if, when the user drills on the main widget, their choices were applied to the dashboard filters. That way, my indicators would reflect what they've drilled into. But that should be an option in the widget settings; other times I have a dashboard with several major widgets and drilling into one should not filter the others. When the user un-drills (clicks the cross or a breadcrumb to return to the overview), that should automatically remove the associated dashboard filter. And if the user alters or removes the dashboard filter, that should carry over to the drill-down breadcrumbs. ... View more

When replacing a server, or testing an upgrade, we often find our clients taking a backup of their Sisense database and restoring it to another server. After updating the server identity in the mongodb, it's pretty much ready to go. However, use dashboards all reference the old server and have to be updated. This is a manual process that the users themselves one dashboard and data source at time. An administrator cannot easily do that work on their behalf. Acknowledging that there is a replace_datasource API call that allows you to apply a new server and data source to a single dashboard, I would love an easier a way to update just the server across all dashboards. ... View more

Current behavior of the Simply Ask feature doesn't support automatic saving of the modified NLQ model to the "*.dash" file. So you loose your development work after exporting the dashboard with already enabled and tuned "Simply Ask" to a "*.dash" file. After importing this dashboard back to Sisense the feature is automatically disabled. Also if a developer will enable it manually it starts running based on the "By Default" NLQ model. This forces to redo all the work on the model back again which is time consuming and not efficient. We expect Sisense to consider in the future the development work on making this more convenient for a BI engineer. If a "Simply Ask" feature will be automatically enabled on an imported dashboard with a corrected model, it would be beneficial for dashboard deploy automation and will reduce unneeded additional manual work on setting up this feature again and again for different working environments for the same dashboard. ... View more

It would be really useful to have a hierarchy filter displaying parent-child relationship. Currently when we create a filter, it just displays all the members in the entity.  If there is a relationship between the members its not possible to identify it directly in 1 filter, the only way around is create dependent filters. But that too would get tedious, as everytime we have go through multiple filters to see the members in each sub filter. Example: If there is a relationship as below: In this case, the table has the name and parent name as 2 separate columns. So the filter could display members as below in a tree format which can be collapsed or expanded, such that there is a check box next to the member and user can select the individual members, or a group of members. It would give the user a clear view of the relationship between different members:       ... View more

We are a multi-tenant software provider and we embed and white label Sisense.  In our setup, we have 2 models.  Model 1 is used by Engineering to create our pre-built dashboards, where we share these with specific groups we've set up so that all of our customers see our pre-built "out of the box" dashboards The second model is what we expose to our Premium users so that they can create their own custom dashboards.   There are times when our customers will create a new, custom dashboard with the second model.  These users sometimes share their dashboard very broadly.  When this happens, there are certain users that wish to remove themselves from the share.  Perhaps they don't have row-level security to see anything.  Perhaps they have changed roles or simply do not use that dashboard. Note that we do not want to allow customers to remove themselves from our pre-built shared dashboards, as this could cause support confusion as to why our analytics solution is enabled but a user doesn't see "all of the dashboards".   With the above noted, we would like a configurable means to show/hide a "leave shared dashboard" dashboard option, based on the model with which a dashboard is associated.  This will ensure that users cannot remove themselves from our pre-built dashboards (we would hide on our model) yet allow them to remove themselves from custom dashboards that were shared with them (we would show on model 2 for self-authoring) When a user leaves a shared dashboard, there should also be configuration options to alert the owner of the dashboard via email.  This email should be capable of white labeling.  It should include dashboard name, who left, and when.  Should there be links to the dashboard in the email, there must be a way to disable hyperlinks in the email. ... View more

Hello There, We need to create a data model with 2 different data sources . One databricks live and another one is an excel file with some additional data . We need to create a combined model so that we can join these two tables and get the result. Currently sisense does not support it and other providers like Power BI and Zoho supports this feature. This is a common use case for our scenario  ... View more