We are experiencing some problems importing some metadata from one instance to another using the metadata export with dependencies.
We export all the metadata linked to one of our programs and try to import it to the target instance.
First of all we realized that in the export file generated the program indicators are not included, which is not a blocking issue but we think it will be also useful to point it out too.
Then the import was successful at the target instance but when trying to edit the program stages of this new program we found two issues : (probably coming from the same error?)
At the programStage edit view we cannot see the name of the program stage. The system just printed $encoder.htmlEncode($programStage.program.displayName). See attached snapshot.
When we click at the update button nothing happens in the instance and if we click at the Cancel button an exception occurs in the browser and at logs files indicates a NullPointerException.
Can you guys take a look at this issues. If we are doing something wrong, missing some steps or whatever. This features will be so useful for us in order to propagate our metadata to other new/existing DHIS2 instances.
Which version of DHIS 2 is this? 2.24 or 2.25? could you also update to latest version of that release, since there have been quite a few updates to the importer in the last weeks.
We are experiencing some problems importing some metadata from one instance to another using the metadata export with dependencies.
We export all the metadata linked to one of our programs and try to import it to the target instance.
First of all we realized that in the export file generated the program indicators are not included, which is not a blocking issue but we think it will be also useful to point it out too.
Then the import was successful at the target instance but when trying to edit the program stages of this new program we found two issues : (probably coming from the same error?)
At the programStage edit view we cannot see the name of the program stage. The system just printed $encoder.htmlEncode($programStage.program.displayName). See attached snapshot.
When we click at the update button nothing happens in the instance and if we click at the Cancel button an exception occurs in the browser and at logs files indicates a NullPointerException.
Can you guys take a look at this issues. If we are doing something wrong, missing some steps or whatever. This features will be so useful for us in order to propagate our metadata to other new/existing DHIS2 instances.
minor comment - it is in fact not the name of the program you cannot see in the edit program stage screen, so it seems the association between program stages and program are not being properly imported.
Lars
···
On Fri, Nov 18, 2016 at 10:56 AM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Marc
Which version of DHIS 2 is this? 2.24 or 2.25? could you also update to latest version of that release, since there have been quite a few updates to the importer in the last weeks.
We are experiencing some problems importing some metadata from one instance to another using the metadata export with dependencies.
We export all the metadata linked to one of our programs and try to import it to the target instance.
First of all we realized that in the export file generated the program indicators are not included, which is not a blocking issue but we think it will be also useful to point it out too.
Then the import was successful at the target instance but when trying to edit the program stages of this new program we found two issues : (probably coming from the same error?)
At the programStage edit view we cannot see the name of the program stage. The system just printed $encoder.htmlEncode($programStage.program.displayName). See attached snapshot.
When we click at the update button nothing happens in the instance and if we click at the Cancel button an exception occurs in the browser and at logs files indicates a NullPointerException.
Can you guys take a look at this issues. If we are doing something wrong, missing some steps or whatever. This features will be so useful for us in order to propagate our metadata to other new/existing DHIS2 instances.
