Sanitise .smodel export

Tim · ‎04-10-2024

When you export a datamodel to a .smodel file, the file includes connection information (server name, password, etc.). I would like an option to exclude that information when I click export. The export dialog already offers check boxes for Data Security, Scope Configuration, etc.; this feature could be just another one that says "Connection Information". Ideally, I'd like it to exclude the connection information by default, so users are forced to explicitly ask to include it, which will remind them to consider the file as sensitive. But I understand if you don't want to change default behaviour that other users are used to. When you import a model that has had this information removed, the import should let you to enter new connection information, or leave it as placeholders like Server=0.0.0.0 and password=Password so you can enter the information after importing. Sisense GIT already removes this information; this feature could work in a similar way. You could even deliberately make GIT's "non-tracked entities" all appear on the list of export options. GIT per this page: https://docs.sisense.com/main/SisenseLinux/asset-translation-and-management.htm?tocpath=Git%20Integration%7C_____3#Non-trac

bminehart · ‎04-09-2024

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.

Tim · ‎06-23-2024

Two problems: Datamodels store old connection information without the user being aware. That increases the chance of accidentally exposing credentials to a different security context. Sisense R&D said that the reason is to show Recent Sources. When you change a dataset, you can end up with two copies of the dataset, which is confusing. Ideas for improvements (take some or all): Sisense could track the Recent Sources separately. Then Sisense could automatically remove empty datasets. Sisense could show empty datasets under Data Sources in the data model editor UI, and give the user a delete button for them. The Data Model editor could have a drag-and-drop to move tables between data sources. When you click export, there could be a checkbox "Remove data source connection information". More detail about the problems here: https://community.sisense.com/t5/support-portal/bd-p/SupportPortal?page=casedetails&caseId=500Pk00000Es4PyIAJ and here:https://community.sisense.com/t5/help-and-how-to/models-have-empty-datasets/m-p/20632#M222

phoebe-rival · ‎11-30-2023

We want to rotate the API key for our system user but need to make sure there's no downtime. This means we need to have 2 keys working in parallel for the same user for a period of time until we can cycle all of our services to pick up the latest api key. The problem is as soon as the API key is rotated, the old key immediately stopped working. Majority of systems out there support key rotation (like allowing a time delay before the old key expires like FB app, or ability to temporary create a second key and then we can promote it as primary once we are ready). Key rotation is a best practice for security principles.

rudyfranco · ‎11-28-2023

When adding a dependent filter, the only [available] lock option is a group lock. It is more useful having the ability to lock the primary filter but allow for dependent filtering. For example, if I lock an audit title, I want to retain the ability to filter specific question(s) within the audit. If both are locked as a group, I have to ensure end users know how to filter through the widget, which can be difficult if the full text of the question does not display or the user is not proficient.

wallingfordce · ‎06-21-2024

When filtering on a numeric field and using a Value type filter, I often want to filter on a dynamic value. As the Ranking type filter can take a formula, I would make good use of a Value type filter that also allowed for a formula.

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Designers cannot save formulas for shared use. This is problematic in two scenarios: 1. End users (our customers’ customers) are Designers 2. Data models are shared across multiple tenants (with row level security) Without this the customer is forced to either manage hundreds of separate data models, which is not sustainable, or to remove all ability to save formulas, which is not acceptable for users. The “Shared Formulas” feature should allow for permissioning; something similar to “limit sharing to users’ own groups” would work.

Tim · ‎06-16-2024

---Summary:--- When you drill, create a filter. Link new filter and the drill-breadcrumbs, so if you change one, it changes the other. Make it an optional, per-widget setting. ---Details:--- Sometimes I build a dashboard with a "main" widget for the user to explore, plus a few indicator widgets above it. It'd be nice if, when the user drills on the main widget, their choices were applied to the dashboard filters. That way, my indicators would reflect what they've drilled into. But that should be an option in the widget settings; other times I have a dashboard with several major widgets and drilling into one should not filter the others. When the user un-drills (clicks the cross or a breadcrumb to return to the overview), that should automatically remove the associated dashboard filter. And if the user alters or removes the dashboard filter, that should carry over to the drill-down breadcrumbs.

Gannon · ‎09-14-2023

When utilising the Fiscal Year functionality, it is frustrating that there is no option to display the calendar year as a formatting option. We are based in Australia and our Fiscal Year starts in July, so our 2023/2024 Fiscal Year (called 2024) runs from July 2023 to June 2024. If I create a simple pivot with our Date, Year (Calendar Year formula) and Fiscal Year (formula in format YYYY/YYYY), then you can see that the date is actually distorted. There is no way to display that this date actually falls in 2023, which is the case for the first two records in the below pivot. Applying a filter with a date range handles this correctly, but it is confusing for our Finance department as to what date this is referring to. I've connected with Sisense support and they've provided a solution for a Date Display Field (thanks @AssafHanina) which does solve the issue, but then we need to have complicated rules for dashboard designers to use X field on their Dashboards but Y fields on filters, etc. I feel like an additional date format of "cy" for Calendar Year would solve this issue from the display side and make things much simpler. Some logic already exists for "yp" for the previous year, this would be very useful for our designers to have this additional option and to keep the date as one field rather than needing a second. Has anyone else encountered this issue or would find this useful?

iberkner · ‎03-21-2024

When a widget returns no data and is displayed in column format - it would be nice to have an option to show the column headers only to give users a reference point as to what data will be shown. Thanks

wallingfordce · ‎06-14-2024

When replacing a server, or testing an upgrade, we often find our clients taking a backup of their Sisense database and restoring it to another server. After updating the server identity in the mongodb, it's pretty much ready to go. However, use dashboards all reference the old server and have to be updated. This is a manual process that the users themselves one dashboard and data source at time. An administrator cannot easily do that work on their behalf. Acknowledging that there is a replace_datasource API call that allows you to apply a new server and data source to a single dashboard, I would love an easier a way to update just the server across all dashboards.

ccoelho · ‎06-12-2024

It would be really useful to have a hierarchy filter displaying parent-child relationship. Currently when we create a filter, it just displays all the members in the entity. If there is a relationship between the members its not possible to identify it directly in 1 filter, the only way around is create dependent filters. But that too would get tedious, as everytime we have go through multiple filters to see the members in each sub filter. Example: If there is a relationship as below: In this case, the table has the name and parent name as 2 separate columns. So the filter could display members as below in a tree format which can be collapsed or expanded, such that there is a check box next to the member and user can select the individual members, or a group of members. It would give the user a clear view of the relationship between different members:

fschleich · ‎08-31-2023

Hello, In a multitenancy environment, it would be useful to be able to define different "look and feel" theme for each tenant. Currently, the one define on the system tenant is applied to every tenant. Thank you.

liegarmina · ‎12-27-2023

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.

sultanahamer · ‎03-05-2024

We have a custom webhook mechanism to alert us for cube build failures. We created a single alert selecting all our cubes and adding the webhook link Given build alerts are owned only by a single person. Ownership transfer of these is helpful when people move out of the team and new person comes in, If not,the alerts created for team will need to be re-created. Also, every time we want to add a new cube to the build alert, the owner of the common build alert should be available else we cannot add alert or will be forced to create a build alert for the absence period of the owner

wallingfordce · ‎06-04-2024

Many of our clients experienced a defect in the Expand Pivot on PDF add-on in which the email body of their dashboard subscriptions included the full Pivot output... instead of the full pivot output being limited to the PDF attachment. With that defect in place for a year, a number of our clients have voiced dismay since the defect was corrected hoping that the defect will come back as a feature. I would image that if enabled as a feature, that Embedded in Email could be unchecked to avoid including large pivot output in the email body. I imagine that users could understand their data well enough to understand whether a dashboard pivot widget would result in pages of output or not, and would be able to make the decision in the share settings for whether or not to Embed in Email or just Attach PDF or both.

alexism · ‎06-12-2023

When Pivot or Table widgets, the options for formatting a datetime column allow showing the date OR the time, with no option to show both together (e.g. if format was "dd/MM/yyyy HH:mm:ss" then we could get "23/10/2022 17:05:21").

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** User parameters must be set and cannot be used for dynamic customizations. When setting up data models, these parameters cannot be included as part of a filter in the underlying query. We would like a way to reference a global or system variable that includes the username of the currently logged in user.

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** For example, we have a system event type that indicates that a restaurant has modified their online ordering hours. Our clients use the indicator for that event type and set it to alert when it gets above 0, as stores aren’t supposed to modify their online ordering hours without owner consent. The problem is that the owner has several stores. They receive an alert when the first store changes their online ordering hours (# of events > 0), but not when a second store does it. The alert is sent at 1 but not 2. The workaround for now is to configure multiple Pulse Alerts, one per store, but that’s only feasible when there aren’t many stores. We have a franchise with over 300 stores! Also, if a store then changes their online hours back, the owner isn’t informed of that either. Can you please add a feature request for an option on the Pulse Alerts to notify on any increase to the value once it’s exceeded the threshold, so the user would receive an alert at 1 and additional alerts at 2, 3, etc.? This would have to be optional and off by default, as you wouldn’t want that to be activated for something that tracked a value that increases often, but the core use case here is for exceptional activity tracking, so the values should rarely increase.

dirons · ‎12-18-2023

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.

Sisense Community

Sanitise .smodel export

dynamic values in text widgets

Datasets UI

Support API Key rotation (2+ keys per user)

Enhancing dependent filtering functionality to allow for a subset-filtering

Allow Value type filters to use formulas rather than just hardcoded values

Shared formulas

Let Drill create a Filter

Enable Calendar Year Date Formatting (instead of Fiscal Year when set)

Show columns on widget when data is empty

Update server (data source) across all dashboards (e.g. after restoring db to a new server)

Ability to create a Hierarchy tree filter

Multitenant - Define one "look and feel" theme per tenantn

Simply Ask modified NLQ model import-export within a *.dash file

Transfer ownership of build alerts to other users

Allow option for Expand Pivot on PDF add-on to also Expand Pivot on Email

Allow date with time formatting in pivot tabel

Make user parameters more dynamic

Send Pulse alert upon any increase of a value after it’s exceeded its threshold

Allow a user to remove themselves from a Shared dashboard (based on model) with email notification