I recently ran into some issues using the new import/export app in 2.30. Everything was re-tested on play.dhis2.org/2.30 after trying on my own instances. Could you let me know any feedback?
Unable to run the metadata dependency export through the UI
Steps to reproduce:
Programs
Select any program
Format - JSON
Compression - Uncompressed
I would use this so I could view the export in the browser before export, or if I want to slightly modify the call prior to exporting.
There is no option to perform a metadata dependency export without sharing like there is for the regular meta-data export. I tried something like the following to exclude the sharing
but could not get it to exclude all the sharing; in this case perhaps my call is just incorrect but it would be preferable if there was an option through the UI
When you import and something goes wrong the log is not very descriptive. You have to look in the browser console and even this does not seem to be very descriptive. For example, here is a file that does not import properly. Everything seems to be ignored and I am not exactly sure why from this message (this is a problem with the default categorycombo I believe)
In <=2.29 it would give you a fair amount of detail as to what was wrong, duplicated or incorrectly referenced and wondering if that will make a comeback?
Thanks
Nick
···
–
Shurajit Dutta (MPH, MHI)
Health Information Systems Adviser
I recently ran into some issues using the new import/export app in 2.30. Everything was re-tested on play.dhis2.org/2.30 after trying on my own instances. Could you let me know any feedback?
Unable to run the metadata dependency export through the UI
Steps to reproduce:
Programs
Select any program
Format - JSON
Compression - Uncompressed
I would use this so I could view the export in the browser before export, or if I want to slightly modify the call prior to exporting.
There is no option to perform a metadata dependency export without sharing like there is for the regular meta-data export. I tried something like the following to exclude the sharing
but could not get it to exclude all the sharing; in this case perhaps my call is just incorrect but it would be preferable if there was an option through the UI
When you import and something goes wrong the log is not very descriptive. You have to look in the browser console and even this does not seem to be very descriptive. For example, here is a file that does not import properly. Everything seems to be ignored and I am not exactly sure why from this message (this is a problem with the default categorycombo I believe)
In <=2.29 it would give you a fair amount of detail as to what was wrong, duplicated or incorrectly referenced and wondering if that will make a comeback?
Thanks
Nick
–
Shurajit Dutta (MPH, MHI)
Health Information Systems Adviser
In terms of your first point, I’ve reported a bug with uncompressed dependency exports (DHIS2-4904 ) – you should be able to successfully do the same dependency export as a compressed file.
I’m working with the Dev team on other issues we’ve encountered with exports/imports (I think the screenshot Muhammad has included below relates to DHIS2-4959), as I’ve not yet been able to successfully export and re-import a dependency XML metadata file in 2.30.
I recently ran into some issues using the new import/export app in 2.30. Everything was re-tested on play.dhis2.org/2.30 after trying on my own instances. Could you let me know any feedback?
Unable to run the metadata dependency export through the UI
Steps to reproduce:
Programs
Select any program
Format - JSON
Compression - Uncompressed
I would use this so I could view the export in the browser before export, or if I want to slightly modify the call prior to exporting.
There is no option to perform a metadata dependency export without sharing like there is for the regular meta-data export. I tried something like the following to exclude the sharing
but could not get it to exclude all the sharing; in this case perhaps my call is just incorrect but it would be preferable if there was an option through the UI
When you import and something goes wrong the log is not very descriptive. You have to look in the browser console and even this does not seem to be very descriptive. For example, here is a file that does not import properly. Everything seems to be ignored and I am not exactly sure why from this message (this is a problem with the default categorycombo I believe)
In <=2.29 it would give you a fair amount of detail as to what was wrong, duplicated or incorrectly referenced and wondering if that will make a comeback?
Is there a timeline for the resolution of this import bug (DHIS2-4959 )? XML dependency exports/imports are still broken in DHIS2 2.30, and a project I’m working on is blocked until I can package up an XML import for sharing with other instances…
Many thanks for any help you’re able to provide in getting this bug resolved…
Subject: Re: [Dhis2-devs] Some issues with metadata dependency export
Hi Nick,
In terms of your first point, I’ve reported a bug with uncompressed dependency exports (DHIS2-4904 ) – you should be able to successfully do the same dependency export as a compressed file.
I’m working with the Dev team on other issues we’ve encountered with exports/imports (I think the screenshot Muhammad has included below relates to DHIS2-4959), as I’ve not yet been able to successfully export and re-import a dependency XML metadata file in 2.30.
I recently ran into some issues using the new import/export app in 2.30. Everything was re-tested on play.dhis2.org/2.30 after trying on my own instances. Could you let me know any feedback?
Unable to run the metadata dependency export through the UI
Steps to reproduce:
Programs
Select any program
Format - JSON
Compression - Uncompressed
I would use this so I could view the export in the browser before export, or if I want to slightly modify the call prior to exporting.
There is no option to perform a metadata dependency export without sharing like there is for the regular meta-data export. I tried something like the following to exclude the sharing
but could not get it to exclude all the sharing; in this case perhaps my call is just incorrect but it would be preferable if there was an option through the UI
When you import and something goes wrong the log is not very descriptive. You have to look in the browser console and even this does not seem to be very descriptive. For example, here is a file that does not import properly. Everything seems to be ignored and I am not exactly sure why from this message (this is a problem with the default categorycombo I believe)
In <=2.29 it would give you a fair amount of detail as to what was wrong, duplicated or incorrectly referenced and wondering if that will make a comeback?
