chore: Use UID in enrollment exporter [DHIS2-17790] #18898
Merged
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.
Harmonize the usage of UID instead of plain String in tracker.
EnrollmentService
and propagate the change until the generic stores.EnrollmentOperationParams
and propagate until the generic stores and until tracker stores when building the queries.EnrollmentRequestParams
are already using UIDs.EnrollmentOperationParams
are now using UIDs.EnrollmentQueryParams
is using hibernate object to build the query. The only field that is now using UIDs isenrollmentUids
and they are passed to the store and the value is used to build the query.Next steps*
TrackedEntity
Event
Relationship
OperationsParamsValidator
deduplication
package