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.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.When viewing a datamodel as "List" remember sort
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.
Feature to export all datamodels from UI
We propose adding a valuable feature to our dashboard UI: the ability to export a comprehensive list of all data models, including both Elasticubes and live models. This enhancement is essential for efficiently monitoring model changes before and after Sisense upgrades. Presently, this process involves manual actions like taking screenshots or exporting a text file using 'si' commands, but it lacks the capability to export live models and essential metadata such as data model type, owner, last modification date, last publication date, activity, and size. By introducing export functionality in formats like CSV, users will be equipped to easily track and compare models, quickly identifying any discrepancies or replacements. This improvement will significantly streamline model management and ensure seamless transitions during upgrades.WAT and ACL Security Model - Default to no access
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'.SQL Snippets Functionality in Sisense Fusion
I have previously worked with Periscope and found the SQL Snippets tool to be very helpful (https://dtdocs.sisense.com/article/snippets#:~:text=To%20create%20a%20SQL%20snippet,button%20and%20name%20the%20snippet.&text=Snippets%20with%20these%20characters%20included,the%20box%20and%20click%20save.) Now my team use Sisense Fusion and we still have a need for this tool, despite it not being a feature in Fusion. We hope to have it available in the future.
