ContributionsMost RecentNewest TopicsMost LikesSolutionsRe: Retrieving total count and paginating large datasets with Compose SDK DRay Thank you for following up and getting an answer for the post steve Thank you for the answer. Do you happen to know if there's a planned timeframe for when the solution will be delivered? Retrieving 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? SolvedRe: Mitigating Optimization Bailouts in Angular with Sisense SDK: Handling CommonJS/AMD Dependencies I get this warnings along with a increase in build time when I inject the SisenseContextConfig in to the application Mitigating Optimization Bailouts in Angular with Sisense SDK: Handling CommonJS/AMD Dependencies I’m experiencing longer build times after integrating the Sisense Angular SDK into my project. Profiling suggests that CommonJS/AMD dependencies in the SDK are triggering optimization bailouts during the build process. Has anyone encountered similar issues with the Sisense SDK? I’m looking for strategies to reduce these bailouts or optimize the integration to better fit Angular’s ES module requirements. Any advice on how to improve build performance while using this SDK would be greatly appreciated! SolvedRe: Help with connecting to Sisense instance DRay the solution from steve worked for me as we already had SSO for embedded dashboards. Help with connecting to Sisense instance The current documentation advises configuring the connection with the following setup: export const SISENSE_CONTEXT_CONFIG: SisenseContextConfig = { url: '<instance url>', // replace with the URL of your Sisense instance token: '<api token>', // replace with the API token of your user account }; This approach involves passing the API token directly from the frontend, which raises security concerns. Can someone please recommend a more secure method for establishing the connection to the Sisense instance, as exposing the API token in the frontend does not seem ideal. Solved