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

Currently, we are using below Rest API to generate a daily report to know the users, groups, roles etc.  /api/v1/users/get We need an additional field (last_password_change_date) for reporting that would tell us when the user changed the password. ... View more

Upon receiving the warning "Maximum number of series (50) exceeded", the warning does not reappear with a widget, dashboard, or page refresh. Instead, a filter change is required in order to trigger it again. IMO the warning should persist with refreshes and be visible every time due to the impact of the limitation being exceed - data is literally missing from the widget and the widget does not reflect the data set expected by the user.  To that end of being clear about the impact of having more series than the limitation allows, the warning would be best reworded to indicate that impact and avoid users making decisions on an uncontrolled subset of data. For example, "Results limited to maximum number of series (50)..." or "Data limited..." This limitation should also be documented in Sisense documentation, but is not currently. ... View more

Required feature to auto manage the license when on SSO. So that if a user drops out of organization or has not utilized the license in the last x days, Then the license is auto recovered from the directory and is free to be consumed. If it possible then please required document  with us. ... View more

Hi, Currently in the filters, we are unable to directly filter a comma separated list of entries. The options available are individually selecting the members, however that can get tedious if the list of entries we need to filter are large. For example, filter more than 100 entries. The other option is using the custom option in the filter. However, that too requires JAQL code which might be difficult for non technical users.  It can be useful to have the option to directly copy paste a comma separated list of entries in the filters instead of multiselecting or using the custom JAQL option.   ... View more

We have had several users complain that the way series selection for charts is not intuitive. Currently, when you have multiple series in a line chart and click on one in the legend, it gets disabled to highlight the others. The intent is to allow focus, but it's the wrong way around - most users expect that the item clicked should be selected and the others hidden. The current behaviour is quite painful if you want to see one series when there are several (you have to click on all the others). Is there a simple way to reverse the selection behaviour, or do we need to look at other options: wrap the control and handle it ourselves (possible?) build some drop-downs/UI to allow selection of whats shown some other neat UI work-around?? ... View more

Is there a way to add dynamic values inside of the text boxes that can be added to Dashboards? As far as I can tell, this is strictly static text. Maybe through scripting or something that is not obvious? If not -- this would be a useful feature to be able to link values to, for example, Dashboard filter values (records from "last 90 days" or "last 30 days") according to what has been configured. ... View more

The number of source of frustration and confusion amongst our users, when building Dashboards, is conflicts/inconsistencies between Dashboard and Widget filters. I have separately suggested that Sisense introduce a visual indicator of widget-level filters and it sounds like that is planned for the future, which is great. Another related feature that a user suggested was a "reset all widget filters" button which would be a single place at the Dashboard level. If the user clicks it, it forces all Widget filters to (a) be deleted (or maybe disabled?), and (b) puts the widget filter settings back in-sync with the dashboard (meaning if the user has selectively toggled off Dashboard filter inheritance at the widget level, that will revert back to the defaults). This is a really quick and easy method to put users back to square one if they have painted themselves into a corner, so to speak. ... 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

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. ... View more

Every day we process our elasticubes and they always process in the same sequence.  Users are able to create dashboards that have widgets from different elasticubes.  However when they select to send the dashboard by email on "Every Elasticube Update" this sends after the first of the elasticubes has processed, rather than waiting until all of them have updated.  This means users are emailed dashboards that have some data correct, and some that is old. I think the solution would be an option to send after all of the elasticubes in the dashboard have updated, or to select a specific one, if the elasticubes generally build in a particular order. It would be good if this could be considered for enhancement as users wouldn't want to receive partially correct dashboards in this situation. Thanks, James ... View more

There are many scenarios where a model contains data for many distinct groups, such as customers, and you want viewers to only have access to the data that pertains to their specific customer. This is easily implemented with row level security, when there is a data column that uniquely identifies each customer. But what if you have a requirement that certain types of viewers should see all columns of data per row, while others should not have access to certain columns? Here is an approach that can be implemented right out of the box in Sisense. The one prerequisite is that any table that contains sensitive data must have a column that uniquely identifies every row, i.e. a primary key column. For every table that contains sensitive data in certain columns, create a new table that contains the original table's primary key column, a binary "switch" column with a name like [Access Allowed] and a column for each of the sensitive columns. Remove the sensitive columns from the original table. Modify the import query to load only the non-sensitive columns in the original table. Modify the import query to load the new table with the primary key and sensitive columns of the original table twice, once with [Access Allowed] set to 1 and the second time with 0 and blank (or null) for all the sensitive columns. Associate the new table to the original table by primary key column Create a dimension table for secure access with the column [Access Allowed]. One row with value 0, one row with value 1. Associate the dimension table with the sensitive data table by the [Access Allowed] column. Set up a data security rule on this column, assigning the secure user group to value 1 and the general group to value 0 If there is a hierarchy greater than two levels of column-level data security, this model can be extended to create additional one-to-one related tables to the original table. ... View more

There are some dashboards where we don't want people messing with the filters.  Or where filters aren't needed to be changed, and we want the maximum "real estate" available for the body of the dashboard. I know you can hide the left- and right-hand panes with script, but this really should be an option exposed in the dashboard designer UI, as a setting for that dashboard. Example: Filter Pane:  Show [default]; Collapsed [but user can expand]; Hidden [user can't expand it]   ... View more

Current behavior of the Simply Ask feature doesn't support automatic saving of the modified NLQ model to the "*.dash" file. So you loose your development work after exporting the dashboard with already enabled and tuned "Simply Ask" to a "*.dash" file. After importing this dashboard back to Sisense the feature is automatically disabled. Also if a developer will enable it manually it starts running based on the "By Default" NLQ model. This forces to redo all the work on the model back again which is time consuming and not efficient. We expect Sisense to consider in the future the development work on making this more convenient for a BI engineer. If a "Simply Ask" feature will be automatically enabled on an imported dashboard with a corrected model, it would be beneficial for dashboard deploy automation and will reduce unneeded additional manual work on setting up this feature again and again for different working environments for the same dashboard. ... View more

Right now, if you're making significant changes to an existing cube, the only way to verify that you haven't broken something is to actually do a build. I'd like a Verify or Validate button, next to the Build button, that would do the initial steps of the build process and then stop.  For example, determine if the metadata in the table can actually be retrieved from the underlying data source.  Or checking datatype mismatches in existing joins.  And so on.  Just leave out the last step where you actually retrieve the full data set and then build the cube. This would save time during the development process. ... View more

We are a multi-tenant software provider and we embed and white label Sisense.  In our setup, we have 2 models.  Model 1 is used by Engineering to create our pre-built dashboards, where we share these with specific groups we've set up so that all of our customers see our pre-built "out of the box" dashboards The second model is what we expose to our Premium users so that they can create their own custom dashboards.   There are times when our customers will create a new, custom dashboard with the second model.  These users sometimes share their dashboard very broadly.  When this happens, there are certain users that wish to remove themselves from the share.  Perhaps they don't have row-level security to see anything.  Perhaps they have changed roles or simply do not use that dashboard. Note that we do not want to allow customers to remove themselves from our pre-built shared dashboards, as this could cause support confusion as to why our analytics solution is enabled but a user doesn't see "all of the dashboards".   With the above noted, we would like a configurable means to show/hide a "leave shared dashboard" dashboard option, based on the model with which a dashboard is associated.  This will ensure that users cannot remove themselves from our pre-built dashboards (we would hide on our model) yet allow them to remove themselves from custom dashboards that were shared with them (we would show on model 2 for self-authoring) When a user leaves a shared dashboard, there should also be configuration options to alert the owner of the dashboard via email.  This email should be capable of white labeling.  It should include dashboard name, who left, and when.  Should there be links to the dashboard in the email, there must be a way to disable hyperlinks in the email. ... View more

Hello There, We need to create a data model with 2 different data sources . One databricks live and another one is an excel file with some additional data . We need to create a combined model so that we can join these two tables and get the result. Currently sisense does not support it and other providers like Power BI and Zoho supports this feature. This is a common use case for our scenario  ... View more

Currently the Analytics screen displays available dashboards in a "list" view or a "tile" view.  The "tile" view includes columns "Name", "Owner", "Data Sources", "Last Published", "Last Modified", "Total Viewers", "No. of Widgets".   This is a request to add a new column "Source Folder".  This would be helpful for users with a large quantity of dashboards as they could sort by the "Source Folder".  In the future, the list view functionality could be expanded to allow grouping by this column which would further consolidate the view. Thank you! ... View more

We need a view that shows us which dashboards are dependent on which table in the datamodel. We want to remove some tables, but because we have many dashboards we don't know where exactly that table data is being used so it's very risky to change/delete tables. The depedency granularity of the data model is good but not enough. ... View more