[FIX] Trace error when transferring a patient#117
Merged
DaeronAlagos merged 1 commit intoremove-custom-frequencyfrom Oct 27, 2020
Merged
[FIX] Trace error when transferring a patient#117DaeronAlagos merged 1 commit intoremove-custom-frequencyfrom
DaeronAlagos merged 1 commit intoremove-custom-frequencyfrom
Conversation
When transferring a patient that has their observations stopped, the outstanding observations are cancelled, but the effective_date_terminated value is missing from the written activity vals. This causes a trace error when the frequency of the new obs that is created is updated Fixes #16841
PeterAlabaster
approved these changes
Oct 27, 2020
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When transferring a patient that has their observations stopped, the outstanding observations are cancelled, but the effective_date_terminated value is missing from the written activity vals. This causes a trace error when the frequency of the new obs that is created is updated
Fixes #16841