You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that when downloading a template for data sets, the list on the Metadata tab shows the categoryOptionCombo names in an inconsistent manner which makes it difficult to work with. For example, for our use case we have two categories called Fund and Project ID, which are combined into an attribute called 'Fund & Project ID'. In the Capture app UI, Fund is selected first, then Project ID. The resulting categoryOptionCombo names in DHIS2 all follow the naming convention [Fund], [Project ID]. However, categoryOptionCombos in the Excel template do not match the categoryOptionCombo names in DHIS2, and instead seem randomly generated, sometimes as [Fund], [Project ID] which is what we are expecting and sometimes as [Project ID], [Fund]. This makes it much harder to use and more confusing for end users. Is this a bug and can it be fixed?
Thanks!
The text was updated successfully, but these errors were encountered:
Hello,
I've noticed that when downloading a template for data sets, the list on the Metadata tab shows the categoryOptionCombo names in an inconsistent manner which makes it difficult to work with. For example, for our use case we have two categories called Fund and Project ID, which are combined into an attribute called 'Fund & Project ID'. In the Capture app UI, Fund is selected first, then Project ID. The resulting categoryOptionCombo names in DHIS2 all follow the naming convention [Fund], [Project ID]. However, categoryOptionCombos in the Excel template do not match the categoryOptionCombo names in DHIS2, and instead seem randomly generated, sometimes as [Fund], [Project ID] which is what we are expecting and sometimes as [Project ID], [Fund]. This makes it much harder to use and more confusing for end users. Is this a bug and can it be fixed?
Thanks!
The text was updated successfully, but these errors were encountered: