Hello,
We have successfully migrated our DHIS2.37 dev instance to DHIS2.41 in order to test and eventually migrate the prod instance.
The first think I have noticed is that the Data visualize with the type “Single value” has changed how its intreprete relative periods. Instead of displaying the relative period as single element (e.g., “Last 12 months”), it now displays each item of the relative period. see the screenshots below:
DHIS2.37
DHIS2.41
Regards;
Hi @didate
Thank you for your feedback. I believe that you prefer that relative period remains in the ‘relative period’ format such as “last 12 months” instead of list of months.
May I ask what is the version of the Dashboard app and if you’ve also updated the app to the latest version?
I don’t know if there’s a way to change this so I’m triaging to @dhis2-analytics .
Thanks!
Hello @Gassim
Hope you are doing good.
We have the Dashboard 100.4.1 . But I think the problem is not related to the Dashboard but to the Data Visualizer app.
The same behavior happens on the DHIS2 play.
Thanks.
Dear @didate - thank you for reporting this issue. It is a known one, based on making sure the user knows what months they are looking at (Since “Last 12 months” could be outdated in a print or screenshot and be misleading) - but definitely agree there are need for improvements. We have this issue currently but it has not been prioritized yet. Jira
Thanks,
Karoline
Hi @Karoline
Thank you for this feedback. Is it possible to put this issue in the prioritized issues ? as you can see the dashboard is really messy with this version.
Regards;
Could I add my voice to prioritising this as an urgent bug? This isn’t really a new feature request, but a bug-fix to an existing feature, which I suspect will prevent a lot of MOHs/organisations from migrating to 2.41.
I’ve looked at the Jira ticket, but it’s registered as a feature rather than a bug-fix, and it’s not scheduled until 2.43! If that’s the target version for a fix, in the meantime would it be possible for version 2.41 to revert the new code that broke this feature back to the legacy code, so that users can continue with upgrades to 2.41 without disrupting their existing dashboards? (As you can see from the screenshots that Lamarana shared, this is not something that could be put into production.) This is currently blocking the upgrade in Guinea, which both the GFF and Global Fund are hoping will facilitate other data quality and ADEx work we’re supporting there.
Many thanks, Sam.
Thanks for flagging this.
(and thanks to @didate for raising it 
)
Hi Phil,
Many thanks for your update to the feature ticket. Do you think it might help if we also created a ‘bug’ Jira ticket for this, explaining how it has broken existing dashboards?
Many thanks, Sam.
Hi Sam,
We’re exploring the issue. I’ve reached out to you guys in a DM.
Dear all,
The above issue is now fixed and released with v101.1.3 of the Data Visualizer app.
Please note that in order to use the above DV app version, you may need to update the dashboard and other analytics apps due to the compatibility requirements:
Kind regards,
Phil
(A big thanks to our Analytics development team!)
Hello @phil
I can confirm after updgrading and testing that this issue is now fixed.
Here is a new screenshot of our dashboard with 2.41
Thanks to all the team. 
Thanks so much for such a quick, efficient fix by the team! 
Regards, Sam.
