DHIS version 2.33 is released

@Pablo
We are using the google play one. We just updated from google play.

Thanks
Mastewal

1 Like

Hi @berhard,

the 2.33 comaptible version will be 2.0.0 which is being tested now and will be released early November.

Thanks!
Marta

1 Like

Great to hear! Thank you!

1 Like

Hello @phil, is there a setting to remove the decimal from the single value chart when required?

1 Like

Hi @ifeanyiokoye,

Yes the number of decimal outputs can be defined in the indicator settings found in the maintenance application. When I was just testing this I found a bug that when the number of decimals is set to zero one decimal is still shown in the analytics outputs.

The bug has been reported, prioritized, and assigned. https://jira.dhis2.org/browse/DHIS2-8033

Sorry for the inconvenience.

Scott

2 Likes

5 posts were split to a new topic: Data entry form is not visible when trying to use the capture app

@Derebe Try clearing your cache using the built-in Browser Cache Cleaning App. Then open the capture app again as you did before.

1 Like

@chase.freeman I did that with no avail. any other suggestion? by the way I am testing it in a local machine not in a cloud server.

1 Like

Hi,

Sigh - it’s really frustrating that this bug has not been permanently fixed yet. I reported it the first time 5 months ago, it keeps on tripping people up.

See JIRA 7301 for a temporary workaround

Best regards

Calle

2 Likes

@sean.leland.dryer Thank you that worked fro me too.

2 Likes

Hello Phil, hope you had a nice holidays, I would like to ask you how to migrate the maps information for the polygons to this version from 2.30, we did an export/import of the OU, the OU tree was imported with no problem but the polygons don´t appear on the GIS app. Could you please give us a step by step on how to import the maps? We will appreciate it very much.

Thanks

1 Like

Hi @jgaf1980,

Thanks for your kind wishes!

I’m afraid I will be on leave until January 6th. In the meantime, I’ll bring your question to the attention of some of my colleagues who may be able to provide some guidance.

It might be impossible to do a direct transfer (export from 2.30 and import to 2.33) of OU metadata due to data model incompatibility (the geometry data model was changed in 2.32, for example).
In that case, you may have to either

  • upgrade a copy of your 2.30 DB before you export your OU metadata, OR
  • import into a 2.30 version and then upgrade to 2.33.

I am just guessing here, but that is what I would try in the first instance.

Kind regards,
Phil

1 Like

Hi @jgaf1980,

As Phil mentioned, you should perform an upgrade in-place on the database rather than attempting to export from 2.30 and import to 2.33. Regarding specifically the organisation unit geometries - due to the difference in geometry field name (coordinates in 2.30, geometry in 2.32+) the import/export will not include geometries in this case - if you duplicate your 2.30 server with its entire database, then upgrade that second 2.30 version to 2.33, then the geometries will be correctly upgraded.

Please let us know if you run into any issues during the upgrade process, and happy new year!

Regards,
Austin

1 Like

Hi Austin and Phil,

Hope great thing are coming to the DHIS2 community in this 2020, thank you for your replies and support with this issue. Finally we got our maps working, thanks to you guys, we did exactly as you told and it worked!!!. We will keep working with this version and let you know if anything new comes up again.

Best regards!!!

1 Like

Hello Elmarie,

Through what channels do you notify Oslo? I’m a fairly new DHIS 2 user. I need to set up data approvals so that unapproved data isn’t accessible to donors. Is there a JIRA bug i can vote for? I’d like to vote/advocate for this as a priority.

Best,
Grace

2 Likes

Dear Grace,

This Community here is a perfectly valid place for you to communicate with us (the Oslo team) :slight_smile:

There is an existing Jira feature (DHIS2-5973), but the status doesn’t tell much at the moment.

Let me provide a little more info…

Firstly, we apologise that this feature was removed in 2.33. It wasn’t our intention; the plan was to replace the functionality. Unfortunately we didn’t get a new app in place, and that was not communicated to this community properly.

The team is currently duscussing the feasibility of recovering the approvals functionality with a core app in 2.34 (which is due in early April).
If the new app is problematic on the timescale for 2.34, then we plan to reinstate the old app that was removed in 2.33. We would like to avoid that for various reasons, but we will do it if necessary to avoid leaving our “approvals” users without an upgrade path.

If you have any specific questions or concerns, you can use this community; including contacting me directly.

Kind regards,
Phil

1 Like

Thanks for this update Philip!

It would be great to reinstate the old app if the revised app is not ready. I will hold off on upgrading (I’m currently using 2.30) until this is resolved. Just nervous about pouring a lot of work into configuring something I won’t be able to use in a few months.

Best,
Grace

2 Likes

Hi Philip,
We were planning to upgrade our DHIS2 instance to 2.33 before April 2020 (we are currently in 2.30), but we can’t afford losing the Data approval. We are therfore planning to remain in 2.30 as long as there is a new version of DHIS2 with functional data approval.

However, we know that 2.30 will not be supported anymore by UiO. Do you think it is a big “mistake” to remain in 2.30 for some more months? Another option would be to upgrade to 2.32, the inconvenient being that it would mean that we would need to upgrade twice this year, which we try to avoid.

Your advice would be very appreciated.

Best regards,
Lise.

Hi @GROUT_Lise,

Officially we stopped supporting 2.30 when we released 2.33 in October.

Naturally we encourage the community to keep as up-to-date as possible; it ensures you have the latest security patches, as well as access to the latest features, bug fixes and performance improvements.

However, unless you have some urgent issues that require fixes present in the newer versions, then I would not describe it as a big mistake to remain on 2.30 for some more months. It really depends on your needs, the cost and logistics of upgrading, and so on. You are in the best position to weigh up the pros and cons for your particular implementation.

In the meantime, we will update the community as soon as we have some concrete news on the new Data Approval functionality.

Kind regards,
Phil

P.S. 2.34 will be available from early April! :wink:

2 Likes

Thank you so much @phil for your quick answer!
There is indeed not perfect solution anyways. We will have a last meeting tomorrow and hope we will take the final decision.
If there is anyway to influence the inclusion of the Data approval in 2.34, let me know where :slight_smile:
Best
lise