Fix: Tracker program "Skip synchronization" not working for attributes or dataValues #105
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
tokland
approved these changes
Oct 8, 2025
tokland
left a comment
tokland
left a comment
There was a problem hiding this comment.
All good. We can just update the PR title with a more friendly description.
nshandra
changed the title
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.
Closes Issue: [1224] Patients' first and last names are not ignored during synchronisation
Jira report: https://dhis2.atlassian.net/browse/DHIS2-19964
When performing a "Tracker programs data sync" or "Metadata synchronization" scheduler job the values of attributes and stage dataElements with Skip synchronization set to true are send to the remote server nonetheless.
The TrackedEntityInstances object always has skipSynchronization == false for the event dataValues.