Export to Excel from the Table widget (without plugin)

dirons · ‎11-16-2023

We would like the ability to export table widget data to Excel. While CSV is supported, we have had customer complaints because they format in the CSV file and forget to save as Excel, losing the work they've done. We prefer this is a Sisense feature over use of a plugin as plugins require additional operational overhead to maintain and upgrade.

Tim · ‎03-11-2024

It’d be nice to save the layout with the .smodel file. That way, I can group related tables together. Maybe also allow comments/colours/tags to show up on the UI. E.g. I could put payroll-database dimensions on one side in blue, operational-database dimensions in orange on the other, and facts in the middle.

jameshaid · ‎09-23-2023

Allow widget designers to turn off the display of the Grand Totals calculation for certain columns in a pivot table. Situations exist for which it is highly beneficial to display the Grand Total of a select few columns in a pivot table, and not to show others as they can be misleading or distract from the primary purpose of the pivot table. I envision an implementation that enables the Grand Total to be toggled on/off for each column, with the default being 'on' for all columns.

soporteparaptx · ‎11-14-2023

Hi, We are facing some issues in the hour timezone related to builds. There's no way to change the UTC setting for the build schedule. It's very confusing and it's generating many issues in timezones when there are changes in the hour due to summer/winter time adjustments. We tried to change the timezone in the upgrade process, but the build schedule only works in UTC. This is a nightmare for data administrators. We need to be able to set the local timezone as the build schedule setting. Best

bmorse · ‎05-13-2024

Currently you only provide a direct link to a dashboard. Allow the ability to have the ID of the dashboard. That way customers embedding the dashboard into their main app can load it natively into their app instead of directing the user directly to the Sisense instance.

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.

DrewGillow · ‎05-09-2024

The in app Look and Feel UI theme editor is an improvement to the CSS editing of the past, but it has removed some capabilities that were possible in the past. Items that should be added to the theme editor Primary Button Outline color Cancel Button Outline color Primary button hover state text color Cancel button hover state text color

JamesDavis · ‎02-27-2024

Every day we process our elasticubes and they always process in the same sequence. Users are able to create dashboards that have widgets from different elasticubes. However when they select to send the dashboard by email on "Every Elasticube Update" this sends after the first of the elasticubes has processed, rather than waiting until all of them have updated. This means users are emailed dashboards that have some data correct, and some that is old. I think the solution would be an option to send after all of the elasticubes in the dashboard have updated, or to select a specific one, if the elasticubes generally build in a particular order. It would be good if this could be considered for enhancement as users wouldn't want to receive partially correct dashboards in this situation. Thanks, James

dougnewton · ‎12-22-2023

Because a non-trivial amount of the population is colorblind, it's a best practice to never rely solely on color when indicating behavior or status of a UI element. The filter-pane buttons are by default, I think, green for positive selection, red for exclusion, and grey for unselected. It would be better if there was also a small icon in the button that would indicate checkmark if positive, "X" if negative, and blank if unselected. Or perhaps, if Unselected (red), show a thin "X" over the whole body of the button. Thank you.

smccartney09 · ‎05-01-2024

My team was adding scripts to widgets to add attributes to the embedded widget and noticed an opportunity to expand what metadata we can use in the scripts. Currently, we're using the widget description (`desc` field) to set a testid attribute, but by default that description is viewable in the embedded widget. I'd love the ability for designers to add key/value pairs to the Widget class metadata that are accessible in the widget script. widget.on('domready', function(w) { const { oid, customMetadata } = w; // customMetadata is the new (optional) property on a Widget const testId = customMetadata['testId']; // a key/value pair added by designer const selectorString = `[widgetid='${oid}']`; const widgetElement = $(selectorString); widgetElement[0].setAttribute('testid', testId); });

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?

fschleich · ‎07-18-2024

Hello, It would be good to be able to export data to Excel from the Dashboard menu. Currently, one dashboard containing 3 widget requires to go to each widget and export to Excel, resulting in 3 diffrente Excel spreadsheets. Users are requesting to be able to export every widget data into one single Excel file / each data widget in one seperated tab. This features exists in ReportManager, so it is difficult to understand why it is not available from the dashboard view. Thank you and regards, Franck

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

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.

fschleich · ‎07-12-2024

Currently, the aggregation function depends on the type of the dimension : - Text or date => Distinct count - Numeric => Sum In our use case, this default assignation is not always accurate as it is sometime required to use Distinct Count with numeric fields. It would be good to hauve the default aggregation function to be choosed by the cube designer, when developping the metadata layer (ElastiCube or Live cube). This way, the dashboard designer will be proposed the accurate function without need to change it. This is particlary interesting with a users population that don't have analytics background and for which choosing the correct agregation function is not obvious. Thank you

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

SamAlbertCSM · ‎07-24-2023

Looking for a way to change the logo based on their corresponding theme. We can create themes for the different companies but there is no option for logo in the Theme and would like to capability to extend the white labeling past just 1 logo

qamardinpal · ‎10-04-2023

Perspectives is a great addition to the application and making only certain parts of the model visible to those dashboards connected to that perspective is excellent. Adding the ability to filter the perspective is something that is required for many of the use cases we have. For example, we have a model that has All Tickets. We have many dashboards that have a locking filter at the top to show only Open Tickets which doesn't look good from a user and design point of view. Being able to create a Perspective and not only be able to refine the columns but also filter to (in this example) Open Tickets only would greatly add to the power and usability of this feature.

zebben · ‎07-20-2023

The idea of this is so you could show the elasticube data on the primary axis, and then potentially low latency data on a secondary axis - allowing easy comparison of live vs historical data

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

Export to Excel from the Table widget (without plugin)

Save layout in .smodel

Allow Grand Totals to not be displayed for certain columns

Build schedule in local timezone

Email templates - provide dashboard id

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

Add more items to look and feel Theme

When using Every Elasticube Update send option send when final elasticube is processed not the first

filter button colors

Ability to add key/value metadata to widgets

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

Every widget data exported into Excel

Sanitise .smodel export

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

Defining the default aggregation function per dimension

Show columns on widget when data is empty

Allow client logo with their theme

Filtered Perspectives

Ability to link a live connection and elasticube into the same widget

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