People sometimes build bad data models. Rather than them doing more training (or asking me to help), you could build a tool that points out common problems. The user would click a button, wait a minute or so, and then get a list of potential problems and suggested changes. The tool would describe an example using their data that they can use to prove the problem (e.g. "filter a widget by Location and Date and then you see it's double counting the Dollars field"); that would be more motivating than an abstract argument. Not only can they debug themselves, doing so will be better than training for teaching them to design better data models. Here are my ideas for issues to look for. They might not always indicate a problem, but you can point them out for the user to decide. Do they use a convention for distinguishing Fact and Dim tables? Typically "fact" and "dim" prefixes for table names. Does any widget use a dim-table field in an aggregation in a Values pane formulas? Does any widget use a fact-table field in a non-values pane, or as a members filter in a formula? Do any dim-tables join to a fact-table via another fact-table? Does any pair of tables have multiple relationship paths of the shortest length? (Should be only one short path and it shouldn't include a fact table, but there might be several longer ones via other fact tables.) Any many-to-many relationships? Sometimes this is intentional and the user is meant to select a single item from a dim-table, so maybe ignore it if all uses in widgets filter one side of the relationship. ... View more

Idea: usage analytics reports can tell what reports use a certain field? Filter by a certain field in the usage analytics report and you will see all dashboards using that field.  It would also be beneficial to track table usage in dashboards too.  Use Case: region will be renamed to region_usa in our sql query and this could potentially break dashboards. to be proactive, i would like to know what dashboards are currently using the field 'region' so that I can redirect them to the correct field, 'region_usa' once the sisense schema & sql has been updated. ... View more

When changing the Elasticube associated with a dashboard, any Pulse alerts built off widgets from that dashboard will not be changed and will continue to be affected by the old Elasticube. This is an issue if you are replacing one Elasticube with another. There is no warning / message when changing a dashboard's Elasticube that pulses will be affected. There is no way to see the Elasticube a pulse is attached to - only the dashboard (but again, changing the dashboard's Elasticube doesn't change the pulses). There is no way to see which pulses are built on top of an Elasticube from the Elasticube screen (unlike with dashboards). I would like the ability when changing the Elasticube for a Dashboard that has Pulse alerts associated to it, give the prompt option to update to the new Elasticube for Pulses as well. This could either be done: Via some new UI Via some warning (similar to when you try and delete a cube with active dashboards / pulses) - but this would then also need the secondary ability to manually change the Elasticube associated with Pulses. ... View more

In browsers, usually links can be right-clicked. You get a menu including "Open in new tab" and "Copy link". Some Sisense links block this behaviour: e.g. the list of dashboards and jump-to-dashboard links. It'd be nice to get it back. To be clear: I do not want every link to open in a new tab. That would be annoying. I just want the option to do so. For example, here's a link where the right-click does work:   ... View more

When I sort cubes in descending order and then click into a cube and come back to the list view I lose sorting. This can be annoying/frustrating. Can you make it so that my sorting remains until I change it? ... View more

WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL ... View more

Currently, builds can only be scheduled in the UTC timezone. This is confusing for someone not in UTC and when you have to coordinate with external processes. The user should have the ability to schedule builds on their own timezone.  ... View more

Creating security rules within the Data Security menu for Elasticubes only allows you to assign users access to values to that are already in your data. If I am creating a rules for user visibility of e.g. individual 'store references' and a new store with reference '1414' is added, I can't create a rule for store 1414 unless it is already in my data. Could there be an option to manually specify the value, rather than having to select a pre-existing value? (I am aware this possible to add via the REST API, but this is a bit fiddly for frequent small edits). ... View more

It appears that once you've created a cube or live data set, you can't rename it. You can duplicate it, but I'd really like to rename some of our models without any of the associated dashboards breaking. ... View more

While editing/viewing a cube data source, you can view the logs of the last build, but can't easily see the overall history of builds for that one cube. It would be nice if you could click on the "..." menu and choose View Build History.  A dialog box would pop up showing the most recent 10 builds (or whatever), sorted by date, with start/end datetime, duration, success/failure, etc. ... View more

I would like to have the possibility for a cube designer to provide a description per dimension. The dashboard designer would be given an help on the meaning of the data he is bringing in his report. The help text would show up on mouse over (tool tips) ... View more

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

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

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

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

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 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

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