Added support to filter data locally having supportPagination false data sources #15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
richardbidin-paragon
approved these changes
Nov 17, 2025
RahulParagon
approved these changes
Nov 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues Closed
PARA-13949
Summary
While fetching data source items, some integrations support pagination (e.g., Slack, Asana, Google Drive, Jira). However, integrations like Amazon S3 currently do not support pagination on Paragon. Although Amazon S3 allow implementing pagination, but we haven’t enabled it because Amazon S3 already returns up to 10,000 records by default.
Current Behavior
If an integration has
supportPaginationenabled in thesourcesconfig:We make API calls using
pageCursorand the search string to fetch filtered data from the backend.If
supportPaginationis disabled:We perform a local filter on the fetched data based on the user’s search input. See https://github.com/useparagon/paragon/blob/fix/PARA-16683/active-campaign-input-title/microservices/connect/shared/ui/sdk/components/SearchableDropdown.tsx#L479
This behavior already exists in the Connect Modal on Connect SDK.
What Was Missing
Headless Connect did not implement this logic, which caused inconsistencies in search behavior across products.
What This PR Does
This PR implements the same search and pagination handling logic in Headless Connect, ensuring consistent behavior across all integration types.
Screenshots
Screen.Recording.2025-11-17.at.16.48.09.mov