Manage BloX stylesheet(s) centrally.

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!

hyiu · ‎08-08-2023

We would like explanations to work with Formulas. This have a few use cases that this benefit. Ideally a user can select a formula and generate a list of explanations with the data fields for the anomalies of the formula.

kwmacd · ‎08-08-2023

We have a few dashboards where the displayed data is only valid when a SINGLE ITEM is selected for a filter. We want to have the standard dashboard filters that our users are used to, but we want to prevent them from selecting more than one item at a time. In the attached image, we want the red highlighted areas to be disabled (not selectable) for non-owners/non-editors of the dashboard. We should be able to publish the dashboard with a default value for the filter and allow them to select a different value, but not multiple values.

markd · ‎07-28-2023

We have tried increasing the row limit for CSV download of live models to 250K rows but Report Manager is still limiting output to 5,000 rows which is the query setting of live models. We would appreciate a specific setting for Report Manager that determines the number of rows or have RM use the row limit defined for the report type (in this case CSV and 250K rows). Changing the query limit for the model does impact the report manager, but this impacts all users and every UI interaction, so the data retrieval volume explodes. There should be an independent setting related to report generation.

OleksandrB · ‎01-16-2024

Hi, for this moment we have such a behaviour: sum(NULL * 10) = NULL but SUM(NULL * [id]) = [id] in the same time if [id] have values (1,NULL) and we will do SUM([id]) = NULL Is it possible to add some toggle in the system how to work with NULL values. For example, if it is disabled it works as NULL is empty and SUM(NULL * [id]) = [id] But if it is enabled, so all NULL should be works as in mathematic SUM(NULL * [id]) = NULL etc

pausan-gh · ‎07-04-2023

Sisense charts show tooltips when you move the mouse above them. When showing those tooltips the website automatically formats numbers in the tooltip in order to simplify the reading and shrinks those numbers if they go above 10k. Most of the times this is what I want as a user, but not always. According to my observations, tooltips stop showing the real number and show a simplification when it goes above 10,000 (e.g instead of showing 16742 it will show 16.7k). This idea would be to allow this number to be displayed in full instead of the shrinked version. Sometimes it is just useful to see the real value and not the simplified one. As a user, I'd like to see the real one sometimes. There are two possible ways of implementing this that come to mind, in the Tooltip section when editing a graph: Add a checkbox, clickable, with the current behaviour by default "[ ] Show raw numbers". This would be below "[ ] Show Total in tooltip" Add a threshold numeric input so that users could manually specify from which number onwards the formatting would shrink (e.g 10,000 by default). "Shrink numbers above: [ 10000]" First option is simpler to understand, second one is more flexible. Right now, the workaround I'm using is to Edit a chart, then click on "Output" in order to see the real numbers as a table, but this is inconvenient. Here is an example of the number I'm referring to, in a chart. You see 15.9k and I'd like to see 15935.

pohwanhan · ‎07-04-2023

Jump to Dashboard allows us to select values within Pivot tables and show the details of the items. This is user friendly and more efficient for users. However, the feature does not work when we call the widget via Sisense.JS.

bminehart · ‎07-03-2023

When creating widgets using the day of the week as a category, the categories are sorted alphabetically by the day of the week (Friday, Mon, Sat, Sun, Thu, Tue, Wed) instead of sorting by the actual order of the days of the week (Sun-->Sat, or Mon-->Sun). Seems like an obvious, and absent, feature.

midkadavil · ‎06-14-2023

Use Case: As a user, I want to be able to share a dashboard with another user with the pre-selected filters so that they can see the same results as I do. Description: The current functionality of the dashboard filters is user-specific, meaning that each user has their own selected filters. However, there is a need to enable users to share a dashboard with another user, ensuring that the pre-selected filters are applied, allowing them to view the same results. This enhancement would allow a user to easily share a dashboard, including their filter selections, with another user. When the recipient accesses the shared dashboard, they would see the same filter settings as the original user, providing a consistent and synchronized view of the data. By enabling the ability to share dashboards with pre-selected filters, users can streamline collaboration, discussions, and decision-making processes. This feature enhances the dashboard-sharing experience and ensures that all parties involved are viewing the same data and insights.

Wantti · ‎06-02-2023

Hi, I want to show in my dashboard the values of the last 12 months period. As I do not want to select the month every month manually, it should be dynamically taking always the last 12 months. So far I am using the advanced settings in the filter: { "last": { "count": 12, "offset": 0 }, "custom": true } The issue is, that my available data is not always up to date. Therefore, I want to select the last 12 months counting the offset back 2 months from the selected month in the filter. As far as I understood is that the offset counts back from the current date disregarding the filters settings. I would need something like thi: { "last": { "count": 12, "offset": 2 (counting from date selected in "sale date" filter) }, "custom": true }

dirons · ‎12-14-2023

We embed and white label Sisense and our premium customers have the ability to author new dashboards with the formulas and attributes we provide. Our users want the ability to create new attributes, comparable to creating a new formulas. Examples: new "Northeast Location" attribute = existing location attribute that we provide where sites = A, B, C new "Shutdown 2023" = existing date field that we provide where date range between X and Y Concatenation of multiple fields to form a new attributes, comparable to Excel new "Is True" type attributes = existing attributes we expose if value(s) = ... Customers want the ability to create their own custom attribute, have then be added to the default values list, in their own "custom" section, where they can search and reuse their own creations. We are a multi-tenant solution provider so tenancy of these custom creation must stay "in tenant" and must do so with us implementing the multi-tenancy feature of Sisense (as we are already deployed and this is not yet robust enough for us to utilize)

zach_myt · ‎12-07-2023

A nice feature in Microsoft SQL Server is the ability to see multiple data sets from queries in stacked windows. Currently only one query can be executed at a time and only display that one query's data set. It would be nice to be able to compare data by having multiple data sets appear at the bottom. Currently I have to open multiple browser windows to compare values and it can get a bit busy. It would be nice to compare 2 or more queries in the same window. Select * from table 1 where id = 123 Select * from table 1 where id = 456 data set for id = 123 data set for id = 456

wallingfordce · ‎05-16-2023

While there are some workarounds... * create a user on behalf of the recipient * create a user that has the email address of an email distribution list * create a forwarding rule in your email ...many of our users would like to schedule some dashboards to be sent via email with support for a pdf attachment to people who are not and will never be Sisense users in their system. Our application (we're OEM) supports this for reports in the application, and there's an expectation that dashboard emailing would exhibit the same support. As it is clients have to create an application user per external recipient, log in as the user and SSO to Sisense to the recipient available as a dashboard subscriber. In some cases, work can be reduced with an application user that represents an email distribution group instead of an account per user, but even that requires a lot of maintenance from dashboard to dashboard as their recipient lists vary so much. The best work around is using forwarding rules in users' email clients so that when they receive the dashboard subscription, it's automatically forwarded to those external recipients. However, the forwarding process is then tied to a specific user's email account which introduces risk should change need making when they're not available, or the organization. If the variability of filters and data security is the concern, then perhaps sending in the context of the owner copy is a step toward an answer without meeting the more robust needs of defining different data security for different non-user recipients of the same dashboard.

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

tjswing · ‎04-26-2023

Currently, when you share a dashboard you can have it email the dashboard out to people following a couple different schedules: Every Elasticube update (with a limit on times per day) Daily (can specify which days and a time) Monthly (can specify which months and what day of the month) The trick is that elasticube updates includes failed updates. I would like to add an option to exclude failed builds from triggering these dashboard update deliveries. Now that we have alerting for build failures, there doesn't seem to be a reason for dashboards to deliver without new information.

hpathare · ‎11-18-2023

the display format of the cube build time is shown as "Nov 8, 2023 2:00:01 AM" We should have option to format it to "11/08/2023 02:00 ' i.e. MM/dd/yyyy HH:mm:ss'

dirons · ‎11-16-2023

We would like the ability to modify attribute names and shared formula names without breaking dashboards or requiring partner plugins.

dirons · ‎11-15-2023

A user would like to remove the title from the secondary indicator. Unchecking the Title box works for only the primary value. They would like the same functionality for the secondary.

gdartigueeis · ‎11-13-2023

There are cases where the Sisense queries have to read from views. Would you consider allowing to issue queries like “ALTER database.materializedView REBUILD” instead of only allowing select commands, in this case this would allow to refresh data that would be selected by the jdbc connector.

Suryakant · ‎11-03-2023

Background and customer pain points Currently Sisense is capable of showing numeric figures in abbreviated format, but only in the American/European short scale form: thousand (k), million (M), billion (B), trillion (T). In east Asian countries, there is a different scale form, so viewing information in these k/M/B/T is very difficult to understand. Non-abbreviated Standard abbreviation (US/Europe) Indian abbreviation East Asian abbreviation 1,000 1 k (thousand) 1,000 1 千 10,000 10 k 10,000 1 万 100,000 100 k 1 lakh 10 万 1,000,000 1 M (Million) 10 lakh 100 万 10,000,000 10 M 1 crore 1000 万 100,000,000 100 M 10 crore 1 億 1,000,000,000 1 B (Billion) 1 arab 10 億 10,000,000,000 10 B 10 arab 100 億 100,000,000,000 100 B 1 kharab 1000 億 1,000,000,000,000 1 T (Trillion) 10 kharab 1 兆 Business case description/value To be able to select the scale form for number abbreviations for different APAC regions as well. Use case A user in Europe is creating a dashboard in Insights with an indicator to show total profit in an Indicator form. Let's suppose that the total profit to display is 1,610,000. 2. Europe user formats the content to abbreviate the display in the short scale form. User will see "1.61 M". 3. A user in Japan is creating the exact same dashboard on the same data. 4. Japan user formats the content to abbreviate the display in Asian scale form. User will see "161 万". 5. A user in India is creating the exact same dashboard on the same data. 6. India user formats the content to abbreviate the display in the India scale form. User will see "16.1 Lakh".

Sisense Community

Manage BloX stylesheet(s) centrally.

Explanations working with Formulas

Limit dashboard filter functionality for viewers

Add a specific CSV row limit for Report Manager

Working with NULL values

Configurable number formatting in tooltips (instead of 12.1k show 12142)

Embed Jump to Dashboard via Sisense.JS

sort day of week data categories correctly

Sharable link with Filters enabled

Select custom period of last 12 months

Allow Designers to create custom attributes comparable to shared formulas

Multiple data sets in one query window

Improved support for sending dashboards to non-users

Filter options that can be viewed , but not filtered

Send out Dashboards Only On Elasticube Build Successes

Format dashboard build datetime

Ability to modify attribute and shared formula names without breaking dashboards

Ability to remove Title (via Design panel) for the secondary value in an indicator

Recompiling views

Number Formatting Support for Japanese Users