Skip to content

FINERACT-2488: Fix duplicate results in /api/v2/clients/search#5485

Open
rhopman wants to merge 1 commit intoapache:developfrom
symbaglobal:FINERACT-2488-fix-duplicate-client-search
Open

FINERACT-2488: Fix duplicate results in /api/v2/clients/search#5485
rhopman wants to merge 1 commit intoapache:developfrom
symbaglobal:FINERACT-2488-fix-duplicate-client-search

Conversation

@rhopman
Copy link
Contributor

@rhopman rhopman commented Feb 12, 2026

The /api/v2/clients/search endpoint returns duplicate entries when a client has multiple identifiers matching the search criteria. When searching by identifier document key, clients with multiple matching identifiers appear multiple times in the result set.

Checklist

  • Write the commit message as per our guidelines
  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
  • Create/update unit or integration tests for verifying the changes made.
  • Follow our coding conventions.
  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
  • This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

@rhopman
Copy link
Contributor Author

rhopman commented Feb 13, 2026

I see that the Verify Liquibase Backward Compatibility check failed. I ran it locally, and on my machine it passes (i.e. the service comes up and the health endpoint reports "UP"). I also cannot think of any reason why the change in this PR would cause this check to break. The error does not seem to be related to the change, as far as I can tell.

Can anyone offer some advice here? Is this check usually reliable?

@rhopman rhopman force-pushed the FINERACT-2488-fix-duplicate-client-search branch from f08f599 to 96926b9 Compare February 13, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant