dhis2-users team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Lavi,

sorry for trouble, see comments below.


On Thu, Jul 24, 2014 at 11:34 AM, Lavi Shpigelman <shpigi@xxxxxxxxx> wrote:

> Hi
>
> I am experimenting with a version 2.15 instance of dhis2.
> To populate this instance, I imported data from a production instance
> running version 2.13 using the web api to grab all the resources in the
> api/resources list (making sure that I get the right resource where the
> resource links point to "dimensions").
> I didn't simply import the metadata resource because I get a 403 error
> when I try to access it. For the same reason I had to skip the users
> resource (perhaps access to users resource blocks me from accessing the
> metaData resource?)
>

Okay. Could you check that your user has the ALL or Export meta-data
authority (through its user roles)? As you probably know this is a more
convenient way of getting all meta-data.


>
> I exported the resources as XML and used the viewClass=export parameter to
> get the right level of detail.
> Import was done with curl, into the metaData resource of my experimental
> system.
>
> After the initial import, some links were missing (such as the lists of
> indicators in dataSets). This was solved by re-importing some of the
> resources until no missing data was seen (verified by comparing api
> resources visually in browser with production system)
>

Okay that's strange.


>
> Once all the metadata seemed in order, I ran the data integrity check and
> got a server error.
> I thought perhaps data integrity checks require actual data values so I
> went ahead and imported all the datavalues using the dataValueSet web api
> resource.
>
> Data integrity still produced a server error so I created the resource
> tables.
>
> Trying to run data integrity check again, I got the error below.
> Any idea what the cause may be?
>

I have seen this error before. It is fixed in latest 2.15 build. The crash
below has two causes. First, he export previously contained empty
<dataEntryForm> elements even for data sets without custom forms. This lead
to the import creating "blank" forms on the receiving side. Second, the
code parsing custom forms had a weakness in that it optimistically tried to
parse the form content without checking for null. Both these issues have
been fixed in latest 2.15 now. You can grab it from dhis2.org/downloads in
40 min.

best regards,

Lars