Give back the ability to manually key in dates
The new filter panel eliminated the ability to manually key in dates. Can we get that back? This is a pretty big regression and I have had many users complain about it. https://community.sisense.com/discussions/help_and_how_to/new-filter-regression/284349Views0likes1CommentHide the "Every ElastiCube update" option on Live Models.
When using a Live Model data source, Pulse Alerts UI changes to reflect this, showing an option for the alert frequency, which only appears when the data source is a Live Model. For a dashboard subscription, the UI does not change with the option for "Every ElastiCube update" being present and seeming to be selectable, though it is not. Please hide this option when the primary data source on a dashboard is a Live Model. Optionally, you could look into hiding only when all widgets on the dashboard use a Live data source and none use an EC data source.14Views5likes0CommentsExcluding Filter Options from a date filter
Hi, I am currently working on a dashboard that requires two date filter. the Date From and Date To filters, to display the latest and earliest dates, which is working perfectly well. However, we would like to prevent users from selecting the first two highlighted options as shown in the attached document in both of these filters. Our goal is to exclude those options from the Date From and Date To filters. Not sure how this can be accomplished. Hoping to get a direction that will help accomplish this request Thanks Tracy13Views0likes0CommentsResponsive pivot table widths
Pivot tables are currently not responsive and it doesn't take up the full width of the available screen in an embedded dashboard. For table widgets, we can set the width to "auto" which uses the whole screen space. Similar functionality can be added to pivot tables to make the dashboards look more formal and appealing.15Views1like0CommentsExport to Excel from the Table widget (without plugin)
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.1.3KViews9likes4Commentsfix issues in bigpanda
Sisense recently rolled out some updates to their analytics platform hosted within bigpanda. During this rollout, Sisense's changes that got rolled out broke a lot of the features that were existing. Tabber widget is broken editing certain widgets is broken new shared vs private operates not as expected. These issues have been reported to bigpanda and they have been trying to get in touch with sisense, but there has been no answer. As a use of the platform, i need these changes fixed. I have followed the basic troubleshooting steps that have been provided to me but this is a sisense issue. Whenever we go to edit certain widgets, we get a request timeout error. Network logs and troubleshooting have been looked at and investigated. PLEASE spend more time on this issue as it is preventing us from moving forward in some areas.38Views0likes0CommentsRequest for API to Programmatically Retrieve Widget-Level Error Responses in Sisense Dashboards
We are currently conducting automated tests on Sisense dashboards to ensure data reliability and visualization integrity. To detect failures, we’ve been using HTML tags to inspect widget responses. However, this approach has limitations especially with indicator widgets that use the <canvas> tag, which restricts DOM-level access and makes it difficult to capture error states. We’ve also explored using the POST /datasources/{cubeName}/jaql API to fetch data, but the payload is large and complex, making it challenging to parse programmatically for error detection. Given these constraints, we’re looking for an API or method that allows us to programmatically retrieve widget-level error responses or statuses from the dashboard. This would significantly improve the reliability and coverage of our automated testing framework Feature Request: Introduce an API or system-level mechanism to: Detect and retrieve widget-level error states Identify query execution failures tied to specific widgets Support automated testing and validation workflows17Views0likes0CommentsFilter dim by aggregate
Summary: New type of filter: Show members of dimX where MyFormula > Y. Similar to a Top filter. Details/Example: I have dimRegion and factSales. I want to report only those regions that have more than 10 sales. I can use a "top" filter to show "top 10 regions by Count(factSales)" I could add a calculated column to dimRegion showing CountOfSales and filter on that. In some cases, neither of the solutions above are appropriate. I want to create a dashboard filter on dimRegion.RegionName that shows only those regions where my measure formula is >10. One use case is that my users might build a complicated aggregate formula, like "(Sum(Revenue)-Sum(Expense))/Sum(Revenue)". They could rebuild that formula as a calculated column, but it means translating it from a Sisense formula into SQL, and it means the formula needs to be updated in two places if it changes. The user might even store the formula as a Saved Formula and re-use it across widgets; I don't want to have to understand the formula, re-implement it in SQL, and verify that my new one is correct, I just want to apply a filter "on the thing my widgets are showing". Another use case is that the dimension might be a non-unique field in a larger table. E.g. If I filter on dimCountry.RegionName. I could add a calculated column "dimCountry.CountOfRegionSales", but it's confusing and risks getting used in a way that leads to double-counting. The "correct" solution would be to create dimRegion and do a field there, but this forces the user to do SQL and data model development, which they might not have the skills for. While I want to encourage best practice (dimRegion), I don't want to force it so aggressively that I'm the only one allowed to use the system.7Views0likes0Comments