Data element with Option Set (List) not filter by code

Support - Assistance technique
,
1

Hello,

Hope everyone is doing well.

We have upgraded our instance from 2.38.1.1 to 2.39.0.0 and we noticed that the options set (list) can not filter by code only by name of the option.

The filter by name and code was working perfectly at previous releases, but at 2.39.0.0 it seems disabled note that we faced a problem at release 2.38.1.1 in the option set regarding capital and small letter filtering (We should search exactly similar name to match the option set name) but it solved in 2.39.0.0 except filtering by code feature.

We need filtering by code for example in ICD-10 codes [J00-J99] Diseases of the respiratory system to identify the patient diagnosis…

Please Advise if anyone has a similar case and if there is any workaround to solve it.

Thanks and regards,

2

Thank you for your post @ayman.tuffaha! Please where are you using the filter (which APP, which API endpoint…etc)? Could you write steps to reproduce/test on any of the play.dhis2.org instances?

Thank you!

3

Thanks for your action response @Gassim the issue I am experiencing is in the Tracker capture App.

We have ICD-10 codes we defined it as an option set as described below:
screenshot with names and codes as seen.

Capture_09
Capture_091891Ă—876 161 KB

Let’s say we would like to search or filter by ICD-10 named “Abnormalities of breathing” as displayed in the screenshot below

Capture_112
Capture_1121212Ă—460 63 KB

There is no problem so far, but if we would like to search or filter by the ICD-10 code instead of the name which is R06 for Abnormalities of breathing as indicated at below screenshot it will not retrieve data from the option set although this was working perfectly at previous releases, but it’s not working in the new release numbered 2.39.0
Capture_1121
Capture_11211220Ă—462 33.2 KB

I hope this clarifies my issue.

Best regards,

1 Like
4

Hi @ayman.tuffaha

I think we have a jira on this: DHIS2-10677
Could you confirm this is the same as your issue? Also - feel free to add some information in the jira.

Caroline

2 Likes
5

Hi @Caroline,

Thanks for your reply, Yes I confirm this is the same JIRA DHIS2-10677 I have added my comment at the JIRA.

Best regards,

1 Like