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

I think table and custom table usage should be added to the scope of usage analytics. I have large data sources that have been around for many years. Often dashboards are unused (which I can currently track with usage analytics) and can be deleted or archived. But the data that drives them is much harder to keep track of. I have no way of knowing which tables are used in dashboards and which ones could be removed. This is especially true for custom tables that eat up build time and might not be used at all. ... View more

Currently the values that get displayed in a "text" based dashboard filter is sorted by default in ascending order. This is ok for most cases. But for certain cases (e.g. date as text) - we wish to showcase values in descending order. Hence, the feature request for allowing sorting in dashboard filters. ... View more

At the moment, the usage analytics functionality is only available for the system tenant. You can monitor activity across all tenants from there. However, this means that you cannot share usage analytics data with designers within the self-contained tenant. ... View more

Currently Embed SDK doesn't provide a function to perform the same function as clicking Restore my default filters button in dashboard filter. It would be great to add it in the future. ... View more

Instead of having to manually set the same format for each date type over and over, it would be nice if you could set defaults for each date type (Year, Quarter, Month, Week, Day) somewhere and have everything default to that with the ability to change away from the default if needed.  This could be done in the same area we set First Day of Week and Fiscal Year for the server. ... View more

1. View all history of builds and its corresponding logs from the cubes. Because, I could not see the last build failure reason, if another build got started. I need to wait for another build to complete or fail. 2. View all history of changes and provide a way to revert as in Google docs for both the cubes and dashboards. Some times, if something went wrong, we should just be able to revert to the previous version and continue from there. 3. Provide a way to view the list of cubes in the queue waiting for the build. Also, allow remove or disable them for a period or rearrange the queue to build. This will help in prioritizing something manual on demand. 4. If a cube build fails due to the memory or other configurations issue, provide suggestions like what has to be changed and based on what before triggering another build. 5. Provide a page to derive the suggested the configurations like memory, cpu, timeouts etc by collecting details like 1. Number of cubes, 2. average cube size, max cube size, min cube size, or number of cubes by size range say <5g, <10G, <20G, <40G etc.., 3. Frequency of the build per cube etc.. 6. Provide a page to view all the slow running dashboards, slow running queries and some suggestions to improve it. 7. Some times, if a dashboard got changed and republished, it is not getting applied to all the users. Provide a way to view the version of the dashboard the user may view. 8. Between builds, if there is not much change in the data, Sisense build should go faster. Provide a way like one common place to build each table from other sources individually and keep it ready. From there, if we build say functional cubes, it should build in flashing fast using the locally stored data. I see the cubes are pulling the data faster from relational db but very slow from mongodb. Now, if we are pulling data from another sisense cube or from the source no big performance difference. 9. Also, I am not sure, if we are restarting the nodes, should we necessarily mark the cubes in queue as failed, instead adding back to the queue as it was before the restart and just marking the actual cube got failed should be good enough. More later .. Thanks, Muthusamy J ... View more

While it is possible to Lock a filter so that users can't change it, sometimes they get confused by the presence of that filter and want to try to change it, which results in a support call to us.  There could also be times when the filter criteria itself is sensitive. We should be able to right-click on a filter and choose "Hide from Viewers". This would also have the benefit of cleaning up the user interface a bit, so viewers don't have to wade through criteria that they can't control anyway. ... View more

Currently File management on Sisense UI under App Configuration shows only storage data. It would be very helpful if various logs can be configured and accessed from file management tab without needing to login to server. Especially in production when there is a need to get the logs for any issue developer has to raise a request with the production support team and wait for their approvals. It would take more than a day to get the files. There is Generate support file option but that is too huge and combines all the logs. ... 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

Currently, dynamicElastiCube supports multi-model dashboards by indicating in the config at a widget level which data source to point to. However, there is no setting to do the same for dashboard filters. Thus, all dashboard filters will point to the "primary" elasticube when routing. This breaks any filter associated with models other than the primary one. ... View more

It's not possible to create a dashboard filter using formulas. I could create a dashboard filter only with variables that are present in a data source. I am able to create a value in pivot table and then use it as widget filter, but it can't be done to other widgets that are not pivots. ... View more

Hello everyone, Since activating the "Export of V2" option, I've noticed that when I export widgets containing sub-totals, the sub-totals don't appear in the Excel export. It would be good to include the sub-totals in the export in order to have a faithful representation of the dahsboard. ... View more

Using the jumpToDashboard plugin, there is a feature enabled with flag "hideSharedDashboardsForNonOwner" that allow the owner of a dashboard to hide dashboards even if shared with other users. The owner is the only one who can see it. The problem of this option is that, when a dashboard is configured to be hidden, the only way the owner has to know this setting is to open the dashboard menu and check the flag status. As a result, it could happen that the owner doesn't have a clear overview of which of his dashboards are visible and which one are hidden to other users. It could be useful to show somehow to the owner, in the tile and list view, if a dashboard is hidden. One simple option is to set a value of opacity for hidden dashboard like "0.65" to distinguish them easily. Attached my implementation of this feature. It's based on 1.3.1 version of jumpToDashboard and adds this feature; it also fixes some issue I found with proxy base url set on the system (win and linux). There is a know bug in this feature (already in the base plugin version); the viewer see the real count of dashboards but then see just the dashboard that are not hidden (e.g.: 5 dashboards counted, but 3 tiles displayed). Here an example of 2 dashboards listed, one hidden and one not: 2024-10-02 - Updated attached version to fix dashboard counter when some dashboard is hidden ... View more

When duplicating an Elasticube with data security rules, the security rules are not duplicated. If I want to create a new version of an Elasticube, distinct from the original, normally I will want to keep the rules, but this does not happen. Being given a choice would be ideal, but if there had to be default behaviour, it makes more sense to just keep the rules, as they can easily be deleted if they are not needed, but re-creating them, even via REST API can be fiddly. ... View more

We have a large number of dashboards and at the moment, find the navigation process for our stakeholders is not ideal as they can only "find" a dashboard if they know what words are used in the title. For example, if a stakeholder searches for complaints but the dashboard title they need is called feedback ... It won't come up as a suggestion.  A solution like having the ability to tag dashboards would massively help Thank you ... View more

Please add support of the First day of the week for the Live models. ... View more