At present we are showing up the selected choice name instead of label in reports. Can we display choices Label in the place of choice name in reports?
Choices Sheet:
List_name: reasons
name: childhood_illness
Label: Childhood Illness
At present we are showing up the selected choice name instead of label in reports. Can we display choices Label in the place of choice name in reports?
Choices Sheet:
List_name: reasons
name: childhood_illness
Label: Childhood Illness
A common way to do that is with the jr:choice-name()
function. You can see more info about that in this response.
Hope that helps! Let us know if you encounter any issues using it.
Hi @marc . Thank you for your quick reply.
`jr:choice-name()β is working only for select_one .If its select multiple the selected options is not showing up in reports .Only the path is showing up .
I am trying to display the selected options with β,β separate and the below calculation is working if i have to show the multiple selected options on from .In reports only the Path is showing up.
concat(jr:choice-name(selected-at(${health_problems}, 0), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 1), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 2), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 3), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 4), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 5), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 6), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 7), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 8), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 9), β${health_problems}β), β,β,
jr:choice-name(selected-at(${health_problems}, 10), β${health_problems}β), β,β)
Can you help me if there is any other solution to show multiple selected choice with label on reports.
Just to make sure I understand, could you sketch or mock up what you hope the report to look like? With that we could discuss it further to figure out the best approach.
Hi @marc
It is very helpful to see what you are trying to achieve there! Displaying the info on the reports tab is indeed different than showing it in the form. Iβll explore a bit to see whatβs going on.
Are you able to share your form for testing? I want to reproduce the behaviour that you are seeing with the jr:choice-name
for a multiple select, especially since you have it working in the form but not the report view.
Hi @marc and @bindugowrig, was this issue resolved - as I found myself in the same situation.
As the screenshots show, the form properly displays the labels but the report displays the choice name.
Please share any updates on this, thank you.
I am not sure if or how @bindugowrig resolved it on their side. Either way, it seems worth exploring further how the report view can be improved.
@michael are report page improvements currently being explored? If not, could that be added as an area of improvement for later consideration?
Thanks @marc, we donβt have any specific improvements planned at the moment for the reports page and I havenβt found anything related in Github.
@kawerewagaba can you tell us a bit more about the users that are seeing this and how they normally use this page? For example⦠is it normally supervisors, admins, or CHWs? Are they searching for specific things or doing random checks?
hi @michael. admins
and chw
see this. they have requested to replace the "programmatic"
responses with more human-readable copy - for a better experience, generally
The ability to translate the report field values (choice names) would also be very useful when the report is viewed in languages other than the language used for storing the values.
Scenario:
There is a project which is entirely used in the Nepali language, but our choice names are close to English. e.g. visited
, not_visited
Because of this, the users can not fully use the app in Nepali.
We also considered using Nepali text in the forms choice names, but that made data analysis difficult for those who didnβt know Nepali.
Thanks for all the great context. I think this opportunity fits well into the βIntuitive UI/UXβ initiative which is the next initiative on the Care Teamβs roadmap. I will add it in the appropriate place to make sure it is addressed.
@binod @kawerewagaba I found an existing issue related to this. I wonder if the βbrute forceβ option mentioned here will be useful for you?