fix: attributes from TET are exported even when TET is not connected to programs [DHIS2-16397] #16148
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.
The current implementation of the analytic table export job has a limitation. When processing attributes, the job only exports columns for attributes that are connected to a program. However, this is not entirely accurate. There can be attributes for a Tracked Entity Type (TET) that are not referenced by any program but should still be exported. Fortunately, this issue has been addressed by this pull request (PR) that resolves the problem.