docs: fix metadata attribute value filter example for 2.42+ - #1777
Open
netroms wants to merge 1 commit into
Open
docs: fix metadata attribute value filter example for 2.42+#1777netroms wants to merge 1 commit into
netroms wants to merge 1 commit into
Conversation
Since 2.42 metadata attribute values are stored as a JSONB map keyed by attribute ID (DHIS2-17482), so the attributeValues.value filter path no longer exists. Filters on attribute values use the attribute's ID as the property name instead.
This was referenced Aug 6, 2026
david-mackessy
approved these changes
Aug 7, 2026
Contributor
|
it's not very intuitive - wonder was this intentional or does it just work this way by accident? |
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.
The metadata API filtering docs still show the pre-2.42 example:
Since 2.42, metadata attribute values are stored as a JSONB map keyed by attribute ID (DHIS2-17482), so the
attributeValues.valuepath no longer resolves and returns400 E1003 Unknown path property. The supported syntax uses the attribute's ID as the property name, which the same page already describes in the filter intro:This updates the example accordingly and adds an example for matching any value with
:!null.Reported on Slack by a community member hitting the 400 on v42+. Needs cherry-pick to
2.43and2.42.AI Assisted