A new endpoint to get all pulse alerts through the API
It would be nice to have an officially supported Events endpoint, that lists all the alerts / pulses / notifications that were sent out when an event was triggered. This allows users to create dashboards giving a quick overview of where problems occur. There already is an /events endpoint, but it is not officially supported and not listed in the APIs, so we were only able to find out about it by creating a support ticket.
API to retrieve Sessions Table details
**Please note this idea was migrated to the Product Feedback Forum from older submission areas** Sisense doesn’t have an API to get data from the Sessions Table. This data is available in the UI only. We would like to be able to use this data in a custom application that we have built. We’d like to see an API that will allow us to get the Session Table details.MongoDB driver-version compatibility
Some of our customers are being forced to upgrade Mongo, and we need to upgrade our drivers in order to match. On 2023.7 we are using driver version 1.3.11 which is not compatible with MongoDB 4.2+ and our customers mentioned they are being forced to go to MongoDB version 5 or 6.Refresh Schema via API
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
Add a specific CSV row limit for Report Manager
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.Enhance Widget Export API
Add the ability to programmatically export a Widget with specific filters and/or to export it as a certain user using the /dashboard/{id}/widgets{id}/ endpoint. User Story#1 As an admin I want to make api calls to the widget pdf export endpoint and include userid and custom filters so that I can download an export on behalf of another user in the system and specify the filters Acceptance Criteria I can pass 2 properties to the export endpoint: User Id and filters Both parameters are optional and can be used separately from each other If a user Id parameter is provided, the Widget is exported on behalf of the provided user including the current filters applied and data security rules. If a custom filters parameter is provided, the Widget is exported with the custom filters. There is no merge between the existing Widget filters and the custom filters parameter. The is an option to provide an empty custom filters parameter, in this case, no filters are applied to the dashboard. User story #2 As a user (not admin) I want to make api calls to the Widget pdf export endpoint and include custom filters so that I can download an export with custom filters Acceptance Criteria I can pass a custom filters parameter to the export to the Export endpoint The custom filters parameter is a jaql query that will replace the current dashboard filters The custom filters will respect my data security I can provide an empty custom filters parameter that will remove all filters from the report.
Idea for password rotation for a live model connection
Hi, I have gone through your connection update process for live models. But As I discussed with sisense team, they don't have any single API for updating connection. As per current scenario we need to follow multiple steps like below:- 1. Get table by: GET /datamodels/datamodelId/schema/datasets/datasetId/tables/tableId. response => tableResult 2. Override table by PATCH /datamodels/datamodelId/schema/datasets/datasetId/tables/tableId} where body = tableResult from the step 1. Only after performing the above steps, you can use PATCH/datamodels?/datamodelId?/schema?/datasets?/datasetId to update the schema for this dataset. So I just want to proposed one idea here that we can use multiple option here like below:- 1. We can provide any Key Vault connectivity for each model where we can store our connection details and we can use them for our model connections. 2. We also can provide a single API where our connection can we updated for all relevant objects & model it self.
