Appointments Tab Username Search Results Are Limited to the Initially Loaded 15 Entries

[nihal467]

Describe the bug

When searching for a user in the Appointments tab, the search only filters through the first 15 names loaded initially, instead of considering all available data.

To Reproduce
Steps to reproduce the behavior:

1. Go to any facility and in the appointments tab
2. search for a user
3. See error

Expected behavior

Necessary request should be fired to get search result from all available data in appointments

Screenshots

[Rishith25]

@nihal467 I would like to work on this

[Sulochan-khadka]

@nihal467 kindly assign me this issue

[ashwinpraveengo]

@nihal467 I would like to work on this issue:

My approach:

• The search should fetch results from the complete dataset, not just preloaded records.
• Modify the search logic to trigger an API request that retrieves and filters results from the backend.

[nihal467]

@Rishith25 its a priority issue, do push the fix by EOD

[Rishith25]

Hey @nihal467
You mean username searching for practitioners right?
If yes can i know which facility have more than 15 practitioners and also credentials becz currently in Poojappura PHC we have only 4 practitoners linked
cc: @Jacobjeevan @rithviknishad

[nihal467]

@Rishith25 feel free to create a new facility with more than 15 practitioners

[rithviknishad]

@Rishith25 you can momentarily set the limit to less than 4 or so; so that resultset gives has results in other pages; this should work as long as the search query is sent to the backend; regardless of the size (15)

[Rishith25]

@nihal467 @rithviknishad

I have added 20 practictioners and all practitioners are visible in dropdown. I think there was no limit set for fetching users and initially all users are loading .

And also we are not passing any search query params in api call

Can you once confirm it or i am missing some thing 👀

[rithviknishad]

@nihal467 I don't see any issue here, this particular API will give ALL users that has a schedule in the facility in the first call to the API itself and the rest is filtered at client side.

[Rishith25]

@nihal467 I don't see any issue here, this particular API will give ALL users that has a schedule in the facility in the first call to the API itself and the rest is filtered at client side.

Yeah that's what I found