Blox Search Field usage for multiple columns
Hi, I'm creating a dashboard with a table with multiple columns containing text. I've created individual filters for the columns. I tried adding the Blox Search Field widget but it is only allowing me to search one column. I created multiple buttons to search and clear each column. Is it possible to create one button that searches all buttons? Here is an image of the Search Field widget with my current implementation:Solved2KViews0likes8Commentsimply Ask Save Function Not Working in Embed SDK Implementation
Hi, I'm working with Sisense's Embed SDK (not iFrame or SisenseJS) implementation and I've encountered a specific issue with the Simply Ask feature. The Simply Ask button is visible and functional in my embedded dashboard, but I'm unable to save any queries created through it. Here's my current implementation: typescriptCopyconst sisenseFrame = new SisenseFrame({ url: 'https://dvunified1.sisense.com/', dashboard: { id: '65118b631a4ea600334e0e7e', settings: { toolbarEnabled: true, toolbarShowDashboards: true, navigation: true } }, settings: { showHeader: true, showLeftPane: true, showRightPane: true, showToolbar: true }, element: document.getElementById('sisense-iframe') }); The interesting part is that: The Simply Ask button appears and works correctly I can create queries and see results However, when trying to save a query, nothing happens I've verified that: I'm using the latest version of Embed SDK The JWT token includes necessary permissions Simply Ask is enabled in the Sisense admin panel The implementation follows the SDK documentation guidelines Is there any specific configuration or permission needed for the save functionality in Simply Ask when using Embed SDK? Or could this be related to the 'volatile' mode setting? Any guidance would be greatly appreciated.Solved551Views0likes2CommentsBreaking changes in 'dashboardLoader' API after upgrade from 2022.8 to 2024.3
Hi, we use Sisense dashboard in embedded Iframe (JS plugin). After upgrading from 2022.8 to 2024.3 our add-on stopped working. From what I see, the API has changed so there are no 'EVENTS' and '$rootScope' objects in the 'dashboard-base.services.dashboardLoader'. I cannot find those changes mentioned in any release notes. The code is following: prism.run([ () => { let dashboardLoader = prism.$injector.get('dashboard-base.services.dashboardLoader'); let origGetDashboardMetadata = dashboardLoader.getDashboardMetadata; // Need to overwrite dashboardLoader.getDashboardMetadata() method in order // to include custom function to run before dashboard load dashboardLoader.getDashboardMetadata = function (...args) { let dashboardLoaderSelf = this; let orig = origGetDashboardMetadata.apply(dashboardLoaderSelf, args); let getWidgetFilterMetadata = new Promise((resolve) => { // Problem here, no 'EVENTS', no '$rootScope' dashboardLoaderSelf.$rootScope.$on(dashboardLoader.EVENTS.FILTERS_LOADED, (e, dashboardOid) => { resolve($$get(dashboardOid)); }); }); ... Can somebody guide me how to achive the same using new API?Solved780Views0likes3CommentsHow to login Sisense with admin ID after onboarded to Azure?
During the installation and minimal 2 IDs will be created under Administrator group. However, after onboarded to Azure and Admin has no way to login using the 2 IDs since these 2 IDs are not exist in Azure. Any dedicated login page available in Sisense to enable Admin login?2.2KViews0likes10CommentsHow to hide environment variables when putting configuration file in plugin folder
I am using Mapbox to create a new widget and add it as an add-on. I noticed that by placing the entire source code in the /plugins directory (including the file containing environment variables - config.js), anyone can access my token and source code. How can I prevent this from happening?1.2KViews0likes3CommentsRetrieving total count and paginating large datasets with Compose SDK
I'm currently working on implementing a custom table to handle a large dataset in Sisense, and I'm encountering some performance challenges related to pagination. Here's the scenario I'm facing: Requirements: Retrieve the total number of records that match a filter condition (to get the total count for display and pagination). Efficiently paginate the results by fetching only the records for the current page, based on page size (e.g., 10, 25, 50 records per page), without retrieving all records at once. The Challenge: While I can use offset and count to paginate the records and fetch only the records for the current page, I don't have a way to determine the total number of records that match the filter condition without retrieving all of the records first. For large datasets, fetching the entire dataset before pagination is causing performance issues, since Sisense retrieves all the records matching the filter condition before applying pagination, which is inefficient. What I'm Looking For: Is there a way to retrieve the total count of records matching the filter condition without fetching the full dataset? How can I fetch only the records for the current page (using offset and count), while still being able to display the total number of matching records? Does anyone has experience implementing efficient pagination in Sisense for large datasets or can share any best practices, examples, or solutions?Solved1.5KViews0likes4Comments