Sisense currently supports Shared formulas to be moved as a part of data Models only. However not all Designers have access to edit/view data models So, they can't move shared formulas from one environment to another via data models Shared Formulas should be exported along-with Dashboards also   ... View more

In the left-hand sidebar where the list of Dashboards is shown, it would be nice if there was a visual indicator of whether a Dashboard that you own is being shared with anyone else. Currently, the only way to determine this is to click the kebab icon (⋮) next to the dashboard name and see if it says "Republish" (indicating the dashboard is currently being shared) or "Share" (indicating the dashboard is not currently being shared with anyone). However, if you are the owner of MANY dashboards, some of which are shared and some of which are not, then it can be very tedious to check this one-by-one. If you hover over a dashboard in the list, a pop-up will display with additional information, one of which is a "Last Published" date/time. However, this doesn't really help. First, it only appears on mouseover, so it doesn't solve the problem of this information being tedious to check/verify (since you still have to check each dashboard one-by-one). Second, the "Last Published" displays if the dashboard has EVER been shared, even if it's not currently being shared with anybody. For example, if I shared a dashboard with Bob, but then later removed him from the share list, then the dashboard is only visible to me and no one else, but the pop-up will still show the last time I published it to Bob (even though he can't see it anymore). There's also a visual indicator, to the left of the dashboards, in the form of an icon that changes depending on the status of the dashboard in question. Unfortunately, this icon only shows the ownership status of the dashboard, not it's share status. That is: it helps you identify at-a-glance (A) which dashboards in a list are ones you own, vs (B) dashboards that someone else owns and has shared with you. However, for the dashboards that fall into (A), there's no indicator as to whether you've shared it or if they are only visible to you.  Perhaps a different icon could be used to indicate each state. Another nice-to-have: for dashboards that fall into (B), i.e. dashboards that someone else owns and has shared with you, perhaps there could be different icons depending on the way it was shared with you. That is: whether the person shared it with you specifically vs shared it with a group that you're part of. Essentially, the icon should indicate all the possible states that a dashboard can be in: Dashboards you own that are not shared with anybody (i.e. only you can see it) Dashboards you own that have been shared with others Dashboards you do NOT own that have been shared with you Dashboards shared with you specifically Dashboards shared with a group you're in ... View more

It's the standard in our industry that products are on sale only for a limited time. For example, tickets being sold for an event aren't sold after the event has occurred. But there's not way to forecast future sales and prevent the forecast from predicting sales after the event has passed and no sales can possibly happen. Instead, customers have to edit every forecast that is currently predicting beyond its event date, every day, to predict only the correct number of future periods.  We'd like a way to predict N future periods, but not past a point in time at which inventory is scheduled to be no longer available. ... View more

We create a basic set of pre-built dashboards that we publish, where business users can view but not modify.  We also have two-tiers of analytics offering for business users (standard and premium).  On our common, pre-built dashboards, which are available to both standard and premium, we would like the ability to expose Simply Ask to only those users of premium (hiding it from those who are standard).   While this may be achievable via a 2-model, 2-dashbaord set approach, we desire to manage a single set of dashbaords and model to simplify deployment overhead and maintenance. ... View more

It would be better to have more control options over exactly when the email report for a dashboard is triggered out to users. Currently we use the option "Every Elasticube update. No more than 1 emails per day" but that has issues: 1) We would only like the email to send if the Elasticube update is successful, rather than every update (including build failures). Otherwise we send a report out with missing data. 2) The rule of "No more than 1 emails per day" doesn't seem to be working properly. Meaning if we refresh the Elasticube more than once per day, users are receiving duplicate reports. ... View more

Currently Notebooks provide a powerful opportunity to access and visualize data utilizing SQL and to add these to fusion dashboards.  Fusion's primary analytics environment allows for powerful dashboard-wide filters.   Currently dashboard filters do not apply to charts or tables which are created through notebooks even if the notebook is pointed to the exact same data table and column as other dashboard widgets.   Please develop the ability for dashboard filters to filter both fusion dashboard widgets and also notebook-based widgets.   ... View more

When using Sisense Live Models, the lowest level of granularity when visualizing date-time data is “Round to 15 min”, not at the minute level. Versus, when using Elasticubes, the most granular option is every minute. It would be incredible helpful for us to have granularity at least to 5 minutes for Live Models because we are working with IoT data that we want to visualize. ... View more

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

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

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

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

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

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

Selecting a value in a row selects only the value and not the row. This prevents passing a specific value unless the unique value is exposed in the table and selected by the user. Right clicking on a value in a row should provide the option to select the specific value that was clicked on, or the specific Row that the value is in. For instance: A pivot table of people with lots of names and dates. If a user finds the person they want to drill into they can drill into the name, but there might be duplicate names, so the drill through will have all the people with the same name. If they select the birthdate of the record it will drill into that birthdate, not specific person with that birthdate. A third unique value has to displayed for each result, like a userID. This value has no meaning for the end user, other than they have to click on the userID and only the userID if they want to drill into that user. There should be a way to select the row, not just a specific value. ... View more

working with the plugin ExtenedPivotOnPDF shows the header of the Pivot only on the first page, doesn’t show starting form the second page. Please add header of table on all the pages. ... View more

Our clients find that the sorting option is not available in Pivot widget, but it's available in Table widget; and on the other hand, we have available the "Drill into" and "Jump To Dashboard" features in Pivot widget, but it's not available in Table widget. That is why I suggest that we should have the feature to "Drill into" and "Jump To Dashboard" in Pivot widget, because that way we'll have all the functionalities needed to sort, drill into and jump to other dashboards in this Pivot widget. With Pivot widget you can drill and jump to: With Table widget it's not possible to drill and jump to:   ... View more

I want an option to remove the "Can Design" role when sharing dashboards (yaml? admin settings? does it already exist?). I dislike the role because: Users don't realise that they're editing a temporary copy, and that the owner can Republish to overwrite. They might make many changes, and then months later someone republishes the owner/master version. I'm not entirely sure if republish always overwrites - if the user has made changes, do they keep their version when you republish or get the new one? If they keep theirs, it makes it confusing when trying to make changes requested by a user, because you make a change, click republish, and then the user forgets to click the revert-to-master-button. Instead of the Designer Role, users can just duplicate the dashboard. That way, no risk of overwrite or confusion.   ... View more