perf: [DHIS2-19724] optimize api-calls on enrollment dashboard #4132
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
Contributor
Author
|
When navigating from the TEI working list to the enrollment dashboard there is a duplicate request made by |
|
src/core_modules/capture-core/components/WidgetEnrollment/hooks/useTrackedEntities.js
Show resolved
Hide resolved
superskip
changed the title
|
🚀 Deployed on https://deploy-preview-4132.capture.netlify.dhis2.org |
|
dhis2-bot
added a commit
that referenced
this pull request
Oct 14, 2025
## [104.1.2](v104.1.1...v104.1.2) (2025-10-14) ### Performance Improvements * [DHIS2-19724] optimize api-calls on enrollment dashboard ([#4132](#4132)) ([955556b](955556b))
Contributor
|
🎉 This PR is included in version 104.1.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
DHIS2-19724
Of the six requests to the
trackedEntitiesendpoint I have removed one (inautoSwitchOrgUnitEpic) and limited the amount of requested data in three.Two of the remaining five requests come from the enrollment widget and the profile widget and can't be removed.
Another two happens during initialization of the enrollment dashboard (one for fetching the tracked entity and one for fetching enrollments). They are done separately for error reporting purposes; the tracked entity request checks if the TE exists, while the enrollment request checks if the user has access to a given program.
The last request comes from
useCommonEnrollmentDomainData, which caches a single enrollment for shared use across all sub-pages of the enrollment dashboard. This might still be a potential candidate for optimization.