Fix: Prevent duplicate data upload for encounter types without ID column #1524
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
ajinkya8010
changed the title
ombhardwajj
force-pushed
the
master
branch
7 times, most recently
from
2b98263 to
cafa6d8
Compare
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.
This PR addresses a common issue where users accidentally upload the same data twice when "Id from previous system" is not filled in, leading to duplicates.
Changes made:
Show warning if certain encounter upload types (like Regular Assessment Encounter) are selected and the Id from previous system column is missing from the uploaded file.
The affected types are:
Child Test new update registration
Pulse Polio enrolment
Regular Assessment Encounter
Updated type registration
The warning appears as an alert before upload proceeds, preventing unintentional duplicate uploads.
Results