I've been trailing the Report Manager add-on and was disappointed to see that the 'Event Based' option for triggering reports did not allow for Pulse Alerts to be used as an Event. It seems the current workaround is to use a tool like Zapier (so the pulse goes out to Zapier via webhook, which then creates the Event and goes back into Sisense, causing the report to be sent. This seems convoluted and I would have thought being able to directly integrate Pulses to trigger Reports seems like a natural fit. ... View more

This is a request to enhance this feature in community thread of the same title. This is useful because it allows users to see all the available dimension for a particular list of filters even if there are no facts for it. I understand that we can also use this community thread; however, this is only limited to 1 dimension. However, right now, it does not work when [Columns] field are added into pivot table. We would like to add a date/day [Columns]. Ideally for us, the left outer join should only be by the [Row] and allow data to be broken into [Columns]. ... View more

This is an "add on" request to this product request. Our customers need to be able to filter on datetime columns using a combination of both the date and the time. I'd like to see this added as a capability of filtering. For example, I'd like to filter records from "0800 yesterday to 0800 today". Or "0800 on Monday to 1700 Wednesday". Or "0800 4/1/23 to 0800 4/5/23". ... View more

When viewing a Dashboard, it is impossible to determine whether there are filters being applied at the widget level without opening each widget individually and reviewing whether (a) the inheriting of Dashboard-level filters has been disabled and/or (b) if additional and/or conflicting filters have been applied at the widget-level. This makes troubleshooting and/or viewing Dashboards very cumbersome. I'd like to see a simple visual flag from the Dashboard view indicating that "there is a filter applied within this widget". It doesn't need to display what that filter is -- only that there is (or is not) a filter within the widget. ... View more

In dashboard filters we currently cannot add custom tool tip to filters. While using the dashboard, it will be helpful to add some tool tip description to the filter which may pop up by hovering around it or through some information icon. For example, if a user needs to use a custom filter, the JAQL syntax may not be intuitive. Using some tool tip, will help a user understand how to use the filter in a JAQL format. ... View more

In report manager, when trying to add recipients for email, we receive sisense user email id suggestions based on keyword entered. This can be confusing to users, as our end users send emails to external recipients(non sisense) and that email id suggestion is sisense internal user email. It will be really helpful if we can have a functionality to disable these email id suggestions from popping up in report manager, and avoid confusion to users.   ... View more

Hi, Working on a dashboard containing 3 pivot tables. Each have a lot of columns. (see print screen attached). In order to have a proper PDF, I need to turn the page format to A0 / landscape When exporting to PDF at the Dashboard level (from the pdf button top right), I access to a PDF setup, where I can choose the layout (landscape) and the paper format (A0), so that all the columns appears properly. In this screen, there is a Save button so that the PDF setup is saved for next time (see print screen) When exporting to pdf at a widget level, the same setup otions are available (landscape and A0), BUT THERE IS NO SAVE BUTTON. I have to redo this setup each time (see print screen). Could we have the the Save button on the widget / PDF option page, same as we have ar the dashboard / pdf option page please ? Thank you ... View more

Today, we can use plugins, dashboard and widget scripts to customize dashboard and widgets for scheduled emails as well as desktop. Same should be available for Pulse scripts which allow to modification of alert JAQL on the desktop, but the same script is not executed when sending alerts/notifications. This causes discrepancy between what the user sees on the desktop and what they receive in email. ... View more

Can we get a "refresh schema for all tables" button? Reason: Our tables are usually "Select * From AnalyticsSchema.ViewName". We control which fields to return by editing the view, not the Sisense table definition. When a field gets added/removed/changed, we need to refresh schema. That's fine to do manually as you're working on that datamodel+views, but we need to refresh all when: We copy a datamodel to a different server. We need to refresh schema at least to double-check that the views are as expected on the new server. (If any fields have changed, then I'll need to go fix any widgets using those fields, or, more likely, update the view to include them.) A view gets edited, perhaps for a different datamodel, and my datamodel hasn't been updated.  I edit several views and want to refresh schema for all those Sisense tables. If I've changed used fields then I'll need to go into each table manually anyway so it doesn't matter, but I've had a case where I've removed unused fields from several views and now I need to click refresh schema on every table individually. ... View more

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

We are trying to investigate how we can trigger a Sisense data model (schema) refresh from the API. This call would be made after a data pipeline schema change. We’ll need the calls to make to "Refresh Schema" how it is done in the UI. Original Community Post by @haarishussain : https://community.sisense.com/t5/help-and-how-to/sisense-api-model-refresh/td-p/21719 ... View more

The email schedules have a limitation when the file used in attachment is large in size. Most email servers have a 25mb max limit.  It would be really helpful, if there was an option to include a downloadable link in the email. When a user schedules an email, with the link option, the attachment is downloaded to a temporary path and the link to that path is provided in the email. Clicking on the link should download the file from the temporary path which can be an s3 bucket or from some server. We can keep a retention policy of few days for the files. ... View more

Currently, any report having a table widget is missing IDs in<td> and <tr> elements of the <table>. We are writing automation testing scripts for which we need to have unique ids for each cell. This is seen in Campaign tables but not for Reports 2.0 dashboards. Cell id, where each cell would have some unique identifier for entire table. ... View more

Within dashboards, the only way to know currently if there is a filter on a widget is to open that widget. This is VERY time consuming if there are multiple widgets within a dashboard (we sometimes have up to 10). Please add an icon at the top of widgets (near the pencil would be great). If the icon is grey, no widget level filter is set. If the icon is colored in, a filter is set. If a filter is set, mousing over the icon should return a preview of what the filter is. ... View more

When the sisense user is deleted the email of this user is still in the recipients list for a report in the Report Manager. If the report Manager is configured to send the reports to external customers, the user who is no longer with the company will be receiving the reports with dashboard data as the reports for the external users are generated using the owner or an additional user. Thanks. ... View more

Hi, Whenever an user with owner access is deleted, all the dasboard created by him are getting deleted. Also, those dashboards shared with others are also deleted. This looks like a critical issue, since the dashboard will be shared among other users, they won't be able to see any dashboard if the user gets deleted. Atleast the dashboard shared with other users should be retained.   Thank You, Deviprasad ... View more

The helm chart supplied with Sisense allows global annotation of all service accounts within the sisense namespace. For example I can annotate an AWS role that is able to be assumed by pods: helm upgrade sisense ${sisense_chart} --namespace sisense \ --reuse-values \ --set global.serviceAccountAnnotations."eks\.amazonaws\.com/role-arn"=${pod_role_arn} While this covers most of the pods by updating all the sisense-* service accounts in kubernetes the ec-build pod (the one that actually builds the elasticube) only uses the default service account in the sisense namespace. A workaround is to annotate the default service account: kubectl annotate serviceaccount default eks.amazonaws.com/role-arn=${pod_role_arn} --namespace sisense But it seems odd that the pod would a) assume the default service account when all other pods have service accounts explicitly defined for them and b) despite having gone to the trouble of wiring up global service account annotations in helm for them not to be applied at the final step of elasticube building. This specific use case is for supplying web identity tokens to a JDBC driver so that you can interact with AWS by using a specific OIDC assumed pod role, rather than using an EC2 role or worse, static credentials in a file or connection string. Even more specifically using CData JDBC parquet driver with S3.   ... View more

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

Simply put, the ability to have a button within the UI for when new users are created within a particular data group (or similar category) to replicate permissions, DS, dashboard sharing, pulse, data model shares, etc.  Even simpler, the ability to have a column within User Mgmt. to show which dashboards are shared with which user.  ... View more