Add functionality for updating the Elasticube a Pulse Alert is associated with
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.
Give developers the ability to explore production without being able to modify
right now we can only allow our developers to either edit models in test or read/use. With read/use they aren't able to actually see the cube in the data page. I need my developers to be able to explore connections, schemas and tables in prod without having the ability to actually make any changes. https://community.sisense.com/category/support/discussions/supportportal#case-detail:500Pk00000mKN4vIAGCreate New Sample Data Sets with more data and more concurrent date ranges
Create a new sample data sets that have a lot more data, date ranges that are current to our dates today, has more scenarios that we see in all customers cases. Like more complex formula creations, displaying a wide range of different KPI's, have a more complex data model to show how dimensions and fact tables can work. Having a sample data set with custom code, custom tables, and custom column. Having one of the tables connect to a DW to show how the connection works as well.
Refresh schema for all tables
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.
SingleStore (MemSQL) Connector: Use CONCAT instead of Pipe operator (||)
The queries Sisense generates in some cases uses the pipe operator (||) to concatenate the strings. However, SingleStore has 2 different modes of treating the pipe operator, depending on @@sql_mode engine variable and PIPES_AS_CONCAT flag: flag is ON: pipe operator is treated as CONCAT and the Sisense-generated query works flag is OFF (default): pipe operator is treated as OR and the Sisense-generated query throws an error In order to avoid the ambiguity, I suggest that SingleStore (MemSQL) Connector uses CONCAT instead of pipe operator by default.Bug in data model list view rename field
Bug: I want to rename a field in my data model. In "Diagram view", that works fine. In "List view", when I click rename on the field, then the textbox accepts letters but when I press the space or arrow keys, the keyboard input gets handled incorrectly: it saves my half-finished new field name.Bug when using left joins in custom tables
In data model custom tables, you can do left joins. For example, Select * From ProductsTable Left Join SalesTable. But there's a bug in the "On" clause causing them to sometimes become Inner Joins. Simple "On" clauses work, such as "On ProductsTable.ProductID = SalesTable.ProductID". Some complex "On" clauses cause the Left Join to become an Inner Join. For example, my custom table below has zero rows in it. Instead, it should return a row for every Cost Pool Group, even if that doesn't have any matching Cost Pools. SELECT * FROM dimCostPoolGroup LEFT JOIN dimCostPool ON dimCostPoolGroup.[Cost Pool Group Code] <> '' AND ( (dimCostPoolGroup.[Cost Pool Group Code] = 'abc' AND dimCostPool.[Cost Pool Code] <> 'abc') OR (dimCostPoolGroup.[Cost Pool Group Code] <> 'abc' AND dimCostPool.[Cost Pool Code] = 'abc') ) NOTE: Do not confuse this with other discussion around left joins in data model relationships. I'm talking about custom tables. In the examples above, none of the tables have relationships.Seing cubes that are shared in the Group screen
Hi, Under Admin / User Management / Groups, we can edit a group. In the window that contains the details of a group, we can see / add / remove users associated with the group. I would like to have the same fetaure with the cubes that are shared with that group. So it would become possible, in the same groupd etail windows for a given group to see / add / remove shared cubes. Thanks you and kind regards, FranckFaster UI for large datamodels
I have a data model with lots of tables (more than 30). That makes the UI painfully slow, e.g. when editing relationships. I think the reason is that it’s calculating where to place them on the screen. I’d like to request an alternative, crude interface that doesn’t slow down for lots of tables. Or make it work for lots of tables – e.g. do the positioning calculations when first opening, but not each time I resize or click on something.
