We have found that if an ACL in a WAT does not match the Elasticube table/column security field, it defaults to providing 'all data'. To avoid a potential human error where a table/column has been renamed, we would like the default position to be 'nothing'.  ... 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

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

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

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

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 NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL ... 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

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

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

Hi, I have issue with setting two date dimensions in dashboard. The goal I want to achieve is to have a history of records, which are also have it's own date dimension. You can download model and dashboard. I would like to have difference in growth ower selected period for defined dates. For example 2 days ago I sold a car for 1000, and yesterday the proce have changed to 1500. The sale date is for today. So the growth over 2 days is 1500, and for 1 day 500. Additionally i would like to compare those values to previous year, and go back with both date dimensions. Tricky part is also, that if there is not sale for this year, PastYear() wont count prior year. I tried to play around with filtered measure plugin, however it doesn't give me exactly what i want. Do you have any suggestions how can I approach such data and 2 date dimensions? Thanks 🙂 ... 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

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

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

We are trying to investigate how we can trigger a Sisense data model (schema) refresh from the API. This call would be made after a data pipeline schema change. We’ll need the calls to make to "Refresh Schema" how it is done in the UI. Original Community Post by @haarishussain : https://community.sisense.com/t5/help-and-how-to/sisense-api-model-refresh/td-p/21719 ... View more

Can we get a "refresh schema for all tables" button? Reason: Our tables are usually "Select * From AnalyticsSchema.ViewName". We control which fields to return by editing the view, not the Sisense table definition. When a field gets added/removed/changed, we need to refresh schema. That's fine to do manually as you're working on that datamodel+views, but we need to refresh all when: We copy a datamodel to a different server. We need to refresh schema at least to double-check that the views are as expected on the new server. (If any fields have changed, then I'll need to go fix any widgets using those fields, or, more likely, update the view to include them.) A view gets edited, perhaps for a different datamodel, and my datamodel hasn't been updated.  I edit several views and want to refresh schema for all those Sisense tables. If I've changed used fields then I'll need to go into each table manually anyway so it doesn't matter, but I've had a case where I've removed unused fields from several views and now I need to click refresh schema on every table individually. ... View more

When viewing a datamodel, there's a button to view as "List" instead of "Diagram". I sometimes use that when I need to methodically check each table. When I first open the datamodel the sort is arbitrary, so I click to sort by Name to go through them alphabetically. It'd be handy if it remembered my choice from my previous session. ... View more

Currently, the "Upsert" build behavior is only available for Build to destination. It would be great if we were able to utilize this feature in our Elasticube model where we are not building to destination. We have numerous tables containing created date as well as updated date that are attached to an id field but are unable to use the updated date field since this will bring in duplicate (or more) rows per id which we can not have. Ranking duplicates and filtering out is not a sustainable with the size of our datasets. The ability to look at the id and updated field would solve this issue without the need for a complex workaround in our data source (Big Query). Thank you! ... View more