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

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Custom queries are case sensitive by default. There are workarounds possible, but are just not productive. Every custom query requires something similar to the following: LEFT JOIN [MedStorageUsers] mu ON upper(mu.UserID) = upper(c.UpdatedBy) I want a global option in Sisense to automatically add tags that makes all custom queries case-insensitive ... View more

It would be nice to allow a Widget to be viewed in full-screen when embed=true. If it could just fill to the size of the iframe that would be better than what it currently. ... View more

We have a use case where we need a Viewer role to have the ability to import and share dashboards. The problem is that those elements are set to canBeOverridden: false. Please change share and import to canBeOverridden: true for the roles API. ... View more

Some of our customers are being forced to upgrade Mongo, and we need to upgrade our drivers in order to match. On 2023.7 we are using driver version 1.3.11 which is not compatible with MongoDB 4.2+ and our customers mentioned they are being forced to go to MongoDB version 5 or 6. ... View more

Under an Admin Account and User Mgmt. it is not easily possible to sort the user role (ascending/decending) like it is with other columns.  License utilization is one thing, but being able to easily filter roles and reassign as needed would be a huge help ... View more

Is there a way to retain formatting when exporting to Excel? We currently highlight rows in red if they meet a condition, but the formatting does not carry forward to Excel ... 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 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

Users would like to be able to define the text sent in the email notification body. Each report sent via Report Manager could have a different text to explain the content of the report / the frequency / the purpose ... For now, it only possible to customize the email body at the server level ... View more

Our primary brand colour is red with our second colour a dark blue, but if I make that the main colour (as I would like), then my buttons become red and cancel buttons need to be another colour. It makes sense for the cancel buttons to be red and I understand the concept in making buttons the same as the primary colour, but in this instance we really want to be able to change that setting and have the buttons be blue so that the cancel buttons could still be red. If I make the primary colour our brand blue then the whole site looks black and white. Suggestion: allow the button colour to vary from the main colour. ... View more

Utilising custom fonts is great to accompany branding/styling guidelines, but a lot of font platforms (such as https://fontwerk.com) don't even provide TTF files anymore and are moving to other formats such as OTF.  FontShop.com also refers specifically to this and that you have to download a type, not a font collection. The FAQs from Fontwerk refer specifically to the fact that they are moving beyond TTF ... But I really need TTF, SVG, EOT, WOFF fonts! No, you really don’t. From experience, we know that this sort of requirement often stems from an old habit or in a case where the old file formats are required because of old hardware. If this is the case or if you are unable to put old habits to rest, we will of course still be happy to produce the formats on request, but for a fee. https://fontwerk.com/en/faq It would be great if Sisense could support font formats in some of the more recent formats. ... View more

As the platform has users across the globe, the timezone chosen for reporting must get aligned with the logged-in user's locale. SiSense already displays the ElastiCube's last build time in the logged-in user's timezone. In similar lines, whenever a widgets reports intra-day transactions / volumes, an option to display the data in logged in user's timezone should be made available by default in the SiSense platform. ... 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

Similar to widow-orphan control of Paragraph page breaks in MS Word... it would be nice to have this in pivot tables too. That is, let's say the existing rows/subtotals in a pivot table take up 20 out of the "rows per page" value of 25.  If the next sub-section to display is going to take 3 rows, great, show that section.  But if the next sub-section is going to show 10 items, it means the subsection/subtotal will be split across two pages.  This is hard to remembe/digest/use when interacting with the dashboard.  With widow-orphan control, it would do a page break "early" before showing that next subsection of 10 items. ... View more

Our clients always have limited inventory to sell. What they sell is constantly changing. When forecasting future results, the prediction frequently projects results beyond the saleable inventory. Our clients a neighbor indicator widget showing the maximum capacity for the given product, and then edit the forecast hardcoding the value into boundary maximum limit. However, this prevents the widget from respecting dashboard filter changes that switch between products. Instead, it would be most helpful if the boundary limitations could also be configured as calculated values from the data. ... View more

While there are some workarounds... * create a user on behalf of the recipient  * create a user that has the email address of an email distribution list * create a forwarding rule in your email  ...many of our users would like to schedule some dashboards to be sent via email with support for a pdf attachment to people who are not and will never be Sisense users in their system. Our application (we're OEM) supports this for reports in the application, and there's an expectation that dashboard emailing would exhibit the same support. As it is clients have to create an application user per external recipient, log in as the user and SSO to Sisense to the recipient available as a dashboard subscriber. In some cases, work can be reduced with an application user that represents an email distribution group instead of an account per user, but even that requires a lot of maintenance from dashboard to dashboard as their recipient lists vary so much. The best work around is using forwarding rules in users' email clients so that when they receive the dashboard subscription, it's automatically forwarded to those external recipients. However, the forwarding process is then tied to a specific user's email account which introduces risk should change need making when they're not available, or the organization.   If the variability of filters and data security is the concern, then perhaps sending in the context of the owner copy is a step toward an answer without meeting the more robust needs of defining different data security for different non-user recipients of the same dashboard.  ... View more

When using Sisense Live Models, the lowest level of granularity when visualizing date-time data is “Round to 15 min”, not at the minute level. Versus, when using Elasticubes, the most granular option is every minute. It would be incredible helpful for us to have granularity at least to 5 minutes for Live Models because we are working with IoT data that we want to visualize. ... View more

This scenario is for embedded Sisense. When creating a new widget from scratch, it seems like the new Widget wizard selects either an Indicator or Pivot Table type of widget depending on the nature of the data being selected by the user. More often that not, this is resulting in a Pivot Table being the automatically selected widget type. Often times, our users do not need to use Pivot Tables; and since Pivot Tables are computationally more expensive to generate, this results in us incurring unnecessary expense for compute on our data warehouse. I don't want to block Pivot Tables -- I just don't want them to be default widget type. I'd rather Sisense use Table as the default widget type; and/or allow Admins to define the default widget type. ... View more