Hello, Currently the number of queries running in parallel during an EC build is set at the server level. With setting "Build / Base Table Max Threads" (4 by default). The optimised number of simultaneous queries is very much dependant on the context of the EC. For instance, an EC with 4 differents date source is more likely to accept a high number of simultaneous queries (spread over the 4 data sources), than an EC with only one data source. Therefore, I would like to suggest to make this setting per cube instead of at the server level. An alternative would be to have this setting at the Data Group level. Thank you and best regards, Franck   ... View more

The number of source of frustration and confusion amongst our users, when building Dashboards, is conflicts/inconsistencies between Dashboard and Widget filters. I have separately suggested that Sisense introduce a visual indicator of widget-level filters and it sounds like that is planned for the future, which is great. Another related feature that a user suggested was a "reset all widget filters" button which would be a single place at the Dashboard level. If the user clicks it, it forces all Widget filters to (a) be deleted (or maybe disabled?), and (b) puts the widget filter settings back in-sync with the dashboard (meaning if the user has selectively toggled off Dashboard filter inheritance at the widget level, that will revert back to the defaults). This is a really quick and easy method to put users back to square one if they have painted themselves into a corner, so to speak. ... View more

Would like an easy way to transfer ownership of objects to someone else.  Or for a super-user admin to be able to "take ownership" of a data model or dashboard.  Will make it easier to deal with when someone leaves the company and they owned things in Sisense. ... View more

This idea aims to help on-premises installations or live connections to better control load. The scenario: we have a big amount of users using the Report Manager plug-in, and we cannot limit the number of reports they can create or even the minimum periodicity for their schedules. Currently any user will be able to create a big number of reports, and those reports in a worst case scenario could be sent every hour. It could case a high usage of server resources. It is possible to setup the number of concurrent reports that will be processed, but depending on the number of reports it could cause bottlenecks and big deliver delays. The idea: adding some new 'admin' settings to Report Manager plug-in: - Maximum number of reports per user: defines the maximum number of reports a unique user can create. We could use 0 for unlimited (current behavior). - Maximum number of reports per user group: defines the maximum number of reports a user group can create. Same ideia as the above, but related to user groups. It could be a unique setting for any user group, or maybe a map with specific limits for each user group. - Minimum periodicity for scheduling: currently Report Manager offers the hours, days, week and months options. For instance, if this setting is set to days, then users will not be able to select hours when creating new schedules. Current existing schedules could be kept. ... View more

We would like to be able to dynamically aggregate different categories of data into a fewer number of categories to make the visualization and analysis of that data cleaner and more Viewer-friendly. Example: I may have records of a color that I want to count on. I may have these possible values: "Red", "RED", "red", "Blue", "BLUE", "blue", "Orange", "ORANGE", "orange", and so on. If I COUNT on these values I may get: "Red": 10 "RED": 7 "red": 12 "Blue": 2 "BLUE": 7 "blue": 22 ...and so on.. I'm asking for aggregation feature that I, as a user, could define based on the values in these records such taht the data above could be represented as: "Red": 29 (i.e., 10 + 7 + 12) "Blue": 31 (i.e., 2 + 7 + 22) ... View more

Hello, It would be good to be able to export data to Excel from the Dashboard menu. Currently, one dashboard containing 3 widget requires to go to each widget and export to Excel, resulting in 3 diffrente Excel spreadsheets. Users are requesting to be able to export every widget data into one single Excel file / each data widget in one seperated tab. This features exists in ReportManager, so it is difficult to understand why it is not available from the dashboard view. Thank you and regards, Franck ... View more

The list of our shared formulas can grow to be quite long.  We would like the ability to search within formulas, just as you can for attributes. ... View more

It’d be nice to save the layout with the .smodel file. That way, I can group related tables together. Maybe also allow comments/colours/tags to show up on the UI. E.g. I could put payroll-database dimensions on one side in blue, operational-database dimensions in orange on the other, and facts in the middle. ... View more

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

Every day we process our elasticubes and they always process in the same sequence.  Users are able to create dashboards that have widgets from different elasticubes.  However when they select to send the dashboard by email on "Every Elasticube Update" this sends after the first of the elasticubes has processed, rather than waiting until all of them have updated.  This means users are emailed dashboards that have some data correct, and some that is old. I think the solution would be an option to send after all of the elasticubes in the dashboard have updated, or to select a specific one, if the elasticubes generally build in a particular order. It would be good if this could be considered for enhancement as users wouldn't want to receive partially correct dashboards in this situation. Thanks, James ... View more

We would like the ability to export table widget data to Excel.  While CSV is supported, we have had customer complaints because they format in the CSV file and forget to save as Excel, losing the work they've done.  We prefer this is a Sisense feature over use of a plugin as plugins require additional operational overhead to maintain and upgrade. ... View more

Hi, We are facing some issues in the hour timezone related to builds. There's no way to change the UTC setting for the build schedule. It's very confusing and it's generating many issues in timezones when there are changes in the hour due to summer/winter time adjustments. We tried to change the timezone in the upgrade process, but the build schedule only works in UTC. This is a nightmare for data administrators. We need to be able to set the local timezone as the build schedule setting.  Best ... View more

Allow widget designers to turn off the display of the Grand Totals calculation for certain columns in a pivot table. Situations exist for which it is highly beneficial to display the Grand Total of a select few columns in a pivot table, and not to show others as they can be misleading or distract from the primary purpose of the pivot table. I envision an implementation that enables the Grand Total to be toggled on/off for each column, with the default being 'on' for all columns. ... 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

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

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

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