Data Value Sets: outputOrgUnitIdScheme not working correctly?

Support - Assistance technique
1

According to the documentation “outputOrgUnitIdScheme” is a valid parameter for the Analytics endpoint however I am not able to get Codes returned.

See here for reproduction on Play. I would expect to see the value of “orgUnit” to be OU_539 as the Code shows here: https://play.dhis2.org/2.35.7/api/organisationUnits/YuQRtpLP10I.json

2.36.3
https://play.dhis2.org/2.36.3/api/analytics/dataValueSet.json?dimension=ou:YuQRtpLP10I&dimension=pe:LAST_MONTH&dimension=dx:s46m5MS0hxu&outputOrgUnitIdScheme=CODE

2.35.7
https://play.dhis2.org/2.35.7/api/analytics/dataValueSet.json?dimension=ou:YuQRtpLP10I&dimension=pe:LAST_MONTH&dimension=dx:s46m5MS0hxu&outputOrgUnitIdScheme=CODE

2.34.6
https://play.dhis2.org/2.34.6/api/analytics/dataValueSet.json?dimension=ou:YuQRtpLP10I&dimension=pe:LAST_MONTH&dimension=dx:s46m5MS0hxu&outputOrgUnitIdScheme=CODE

https://jira.dhis2.org/browse/DHIS2-11769

2

I agree. I get the same results on all three versions, and it looks like a bug to me. Please write a Jira ticket if you would.

outputDataElementIdScheme appears to be similarly broken. Both should be fixed.

However outputIdScheme=CODE works. This sets the scheme for both output orgUnits and dataElements. If you don’t mind having both of them returned as codes, this might be a workaround for you for now.

1 Like
3

Thanks for validating Jim. Ticket here: [DHIS2-11769] - Jira

We may be able to work out adding code mappings to the data elements between the two servers that we are integrating.

1 Like