Aggregate Categorical Data to Simplify Analysis

bminehart · ‎05-08-2023

We would like to be able to dynamically aggregate different categories of data into a fewer number of categories to make the visualization and analysis of that data cleaner and more Viewer-friendly. Example: I may have records of a color that I want to count on. I may have these possible values: "Red", "RED", "red", "Blue", "BLUE", "blue", "Orange", "ORANGE", "orange", and so on. If I COUNT on these values I may get: "Red": 10 "RED": 7 "red": 12 "Blue": 2 "BLUE": 7 "blue": 22 ...and so on.. I'm asking for aggregation feature that I, as a user, could define based on the values in these records such taht the data above could be represented as: "Red": 29 (i.e., 10 + 7 + 12) "Blue": 31 (i.e., 2 + 7 + 22)

bminehart · ‎05-08-2023

Scenario: embedded Sisense By default, when creating a new widget, Sisense puts the user into the widget "Wizard Mode", which then requires the use to click "Advanced Configuration" to view the full-feature widget editor. We don't want our users to use "Wizard Mode" and to always be placed directly into "Advanced Configuration". This should be a configurable setting at the Admin level.

bminehart · ‎05-08-2023

This scenario is for embedded Sisense. When creating a new widget from scratch, it seems like the new Widget wizard selects either an Indicator or Pivot Table type of widget depending on the nature of the data being selected by the user. More often that not, this is resulting in a Pivot Table being the automatically selected widget type. Often times, our users do not need to use Pivot Tables; and since Pivot Tables are computationally more expensive to generate, this results in us incurring unnecessary expense for compute on our data warehouse. I don't want to block Pivot Tables -- I just don't want them to be default widget type. I'd rather Sisense use Table as the default widget type; and/or allow Admins to define the default widget type.

bminehart · ‎05-08-2023

This is for LiveConnect data sources using Snowflake. We cannot filter Datetime columns at the hours level. Either "last n" hours or "between 08:00-12:00" as example. I would like to see this added as a capability of filters.

vbaskaran · ‎05-08-2023

Current Behavior: When user selects filter options such as Contains, Does not contain, Starts with, Does not start with , End with , Does not end with etc. , the resulted suggestions can only be viewed , but cannot be filtered. Proposal Users should be able to select a filter option, enter a value and use the suggestions to filter. Currently its giving an inconsistent user experience (Some options are filterable such as Is, Is not, & few others are not) OR, should display an appropriate label to say the least . I initially considered this as a bug ,and later realized as a product design. Thanks

ndewinkle · ‎05-01-2023

To ensure security and compliance for HIPAA, we need to know when users export data. Specifically, we want to know how many rows were exported so we can check for malicious use.

ehannscott · ‎04-28-2023

WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL

Anonymous · ‎04-28-2023

When working with filters and long lists of available values, NULL values in columns are represented as N/A but appear somewhere within the list. This makes it very hard to search for them when you work with a very long list of possible values and want to make sure to exclude NULL values. It would be nice if NULL values could always be pinned to the top of a search list so they can easily be excluded from a filter selection.

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

irismaessen · ‎04-20-2023

Currently every BloX widget has its own stylesheet that is defined separately from the look and feel of the rest of the Sisense application (apart from the action buttons, for some reason). This is understandable for some out-there cases, but in many cases I've had to work with Blox, what I really want is for my Blox widgets to fit in with the look and feel of the rest of the dashboard -- in essence to use the same default stylesheet, if not as the whole dashboard application, then at least as other BloX widgets. The current 'stylesheet' in the widgets could then be used to overwrite any details for that particular widget, instead of it functioning as a full stylesheet every time. Thank you!

jirazazabal · ‎04-19-2023

Hi, Many customers are asking to enable two-factor authentication. It will be a very important security enhancement. Thanks

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

soporteparaptx · ‎04-19-2023

Hi It's a need that we have found many times, related to the availability to design the dashboard layput with a dinamic grid, not just columns and widgets in the same column. Users demand more flexibility on the layout design.

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Sisense doesn’t have an API to get data from the Sessions Table. This data is available in the UI only. We would like to be able to use this data in a custom application that we have built. We’d like to see an API that will allow us to get the Session Table details.

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** We are hosted on Azure for Sisense. When looking at hosting Snowflake in AWS, it complicated out could architechture too much. We are looking for an option to continue to host using Azure, but also benefit from Snowflake.

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

Community_Admin · ‎04-17-2023

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** The Data Designer, when modeling an Elasticube or Live model isn’t able to define the default aggregation method. When adding a measure to a widget, an aggregation method is automatically applied. The Dashboard Designer can choose the aggregation method via a menu, but a regular click will always choose a predetermined system-wide defauilt (distinct count or sum). In some cases, the aggregation applied is not relevant and could lead to invalid results. I would like to see a feature that allows a Data Designer, when designing the data model, to define the default aggregation for a column. A Data Designer has the knowledge of the data model and what aggregation is best used for it. This ability would assist Dashboard Designers in correctly using the model.

Sisense Community

Aggregate Categorical Data to Simplify Analysis

Disable Wizard Mode for New Widgets

Allow the default widget type to be configurable by Admins

Hours-Level Filtering for Datetime Columns

Filter options that can be viewed , but not filtered

Log number of rows exported when exporting to CSV.

WE NEED THE ABILITY TO DO A LEFT JOIN WITHIN THE SISENSE DATA MODEL

Pin NULL values on top of search list (filter selection)

Filter by both the dimension and break by on the dashboard

Manage BloX stylesheet(s) centrally.

Two-factor authentication

User password expiration

Dashboard grid by design

API to retrieve Sessions Table details

Expand Build to Destination (B2D) to include Snowflake on Azure

Apply case-insensitivity option across all custom queries

Allow measures to have default aggregations