Filter by both the dimension and break by on the dashboard

ScheurK · ‎04-24-2023

Hi all, Repost of my question in the community forum: Let's say I have a bar chart in my dashboard displaying number of customers over time with customer segments (small, regular, top) in the break by field. When I turn on 'widget affects dashboard filters' I noticed that the dashboard filters are not affected by whatever is in the break by field. I would like an option where I can filter the dashboard by both. From a user perspective it also makes sense. E.g., when a user clicks on the top segment in february 2022 then all other widgets in the dashboard show the values for top customers in february 2022. Kind regards, Kevin

soporteparaptx · ‎04-19-2023

Hi, Many customers are asking about secutiry concerns. One of it is about the feature of set a time when the password expires. For example, if a viewer has set a password expirtation time to 60 days, he needs to change the password into these days. Days before the expiration he will be notified. Thanks

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Custom queries are case sensitive by default. There are workarounds possible, but are just not productive. Every custom query requires something similar to the following: LEFT JOIN [MedStorageUsers] mu ON upper(mu.UserID) = upper(c.UpdatedBy) I want a global option in Sisense to automatically add tags that makes all custom queries case-insensitive

ehoskin · ‎11-14-2024

It would be helpful to choose where on a dashboard to add a new widget rather than it only being added to the bottom of the dashboard.

m3ac-johnsonb · ‎10-31-2024

It would be great if we were able to setup Active Directory for an individual tenant while having SSO enabled for another tenant. This would help us differentiate between our external customer facing and internal BI.

naga · ‎10-15-2024

Currently File management on Sisense UI under App Configuration shows only storage data. It would be very helpful if various logs can be configured and accessed from file management tab without needing to login to server. Especially in production when there is a need to get the logs for any issue developer has to raise a request with the production support team and wait for their approvals. It would take more than a day to get the files. There is Generate support file option but that is too huge and combines all the logs.

joeshepper · ‎10-08-2024

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.

kseri · ‎09-30-2024

Hello everyone, Since activating the "Export of V2" option, I've noticed that when I export widgets containing sub-totals, the sub-totals don't appear in the Excel export. It would be good to include the sub-totals in the export in order to have a faithful representation of the dahsboard.

zebben · ‎09-24-2024

We have a large number of dashboards and at the moment, find the navigation process for our stakeholders is not ideal as they can only "find" a dashboard if they know what words are used in the title. For example, if a stakeholder searches for complaints but the dashboard title they need is called feedback ... It won't come up as a suggestion. A solution like having the ability to tag dashboards would massively help Thank you

btrevizan · ‎08-01-2024

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.

bminehart · ‎07-17-2024

The only way non-Owners of Dashboards become aware of a Dashboard being republished is if (a) they happen to notice changes in the Dashboard design since the last time they viewed the Dashboard, or (b) if the Dashboard Owner (outside of Sisense) proactively notifies Viewers that they have republished the Dashboard. I would like to see a feature where there is a visual indicator to non-Owners that informs them that "This Dashboard has been republished by the Owner since the last time you viewed the Dashboard." An Even Better If would be to allow the Owner to add notes when they republish, and these notes could be visible to non-Owners the next time they open the Dashboard.

cjakerle · ‎06-27-2024

Currently the Usage cube has a dimUsers table that has User Name but it is the email address. It can be tough to know just from an email address, who the person is. It would be nice to have the First name and Last name of the user available. Certainly I could try to make a connector into the mongoDB and lookup the First/Last based on the user id. But a) I don't want to modify the out of the box usage cube and b) that seems like a lot of work for something that could be added as part of the out of the box usage cube. Thanks, Chris

wallingfordce · ‎06-21-2024

It takes 5-10 seconds to load the Manage Cases page in the Support Portal. It takes even longer to open a specific case. A case can only be opened in the same window as the Manage Cases page. To go to another case requires going back to the Manage Cases page first and waiting for it to load again. Please allow cases to be open in a new tab so that the Manage Cases page doesn't have to be reloaded so frequently, and many cases can be open and loaded concurrently rather than one at a time. Thanks for considering.

joeshepper · ‎06-13-2024

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

wallingfordce · ‎05-15-2024

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.

ccoelho · ‎04-11-2024

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.

ccoelho · ‎04-09-2024

Currently, if we export the pivot as an excel/csv, there is no indication of the date range it was run for in the output file. It will be really helpful to have control on the exported output in excel or csv, such that we can include the date range of the result or other filters applied in the output.

bminehart · ‎04-08-2024

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.

sultanahamer · ‎03-05-2024

Cube build alerts via webhook should receive which cube has triggered the alert. This is required especially when we configure a single alert for multiple cubes As of now, we are only receiving following info. {buildSuccess: false, name: Cloned sisense alerts, type: build} With this info, we do not understand which specific cube has failed.

lbueno · ‎02-08-2024

This idea aims to help on-premises installations or live connections to better control load. The scenario: we have a big amount of users using the Report Manager plug-in, and we cannot limit the number of reports they can create or even the minimum periodicity for their schedules. Currently any user will be able to create a big number of reports, and those reports in a worst case scenario could be sent every hour. It could case a high usage of server resources. It is possible to setup the number of concurrent reports that will be processed, but depending on the number of reports it could cause bottlenecks and big deliver delays. The idea: adding some new 'admin' settings to Report Manager plug-in: - Maximum number of reports per user: defines the maximum number of reports a unique user can create. We could use 0 for unlimited (current behavior). - Maximum number of reports per user group: defines the maximum number of reports a user group can create. Same ideia as the above, but related to user groups. It could be a unique setting for any user group, or maybe a map with specific limits for each user group. - Minimum periodicity for scheduling: currently Report Manager offers the hours, days, week and months options. For instance, if this setting is set to days, then users will not be able to select hours when creating new schedules. Current existing schedules could be kept.

Sisense Community

Filter by both the dimension and break by on the dashboard

User password expiration

Apply case-insensitivity option across all custom queries

Ability to add widget anywhere on dashboard

Alternate authentication method for different tenants

Access various logs from Sisense UI under file management option

Add functionality for updating the Elasticube a Pulse Alert is associated with

Add subtotals to Excel exports when ExcelV2 is enabled

Means to tag dashboards to enable search

Ability to change timezone for build schedules

notification to Viewers after Dashboard is republished

Provide User Name in addition to email address in Usage cube

Allow opening support cases in a new tab

Allow creation of security rules for data that does not exist yet

The "Maximum number of series (50) exceeded" warning, reword it, make it sticky, and document it.

Ability to add a comma separated list of entries in a dashboard filter

Exported excel file to include date range the dashboard/widget was run

button to reset all widget-level filters

Cube build alerts via webhook should receive which cube has triggered the alert

Report Manager - Add new admin settings to better control schedule limits