dhis2-users team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

It can be hard to tell.We need much better information here as the log
reports are pretty useless.

You should probably gather all of your data element ids and check them one
by one against whether they are available before attempting an import. This
can be done through the API and scripted of course. Same for orgunits and
catcombos.

Regards,
Jason


On Wed, Feb 25, 2015 at 5:33 AM, Knut Staring <knutst@xxxxxxxxx> wrote:

> As can be seen from the Import Summary below, I have around 38K values
> that don't get imported because the corresponding data element is not found.
>
> Suggestions as to how I can find out WHICH data element(s) that is not
> linking?
>
> Import summaryImport countTypeCountImported453814Updated0Ignored38209
> ConflictsElementDescriptiondataelementData element not found or not
> acccessible
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> Norway: +4791880522
> Skype: knutstar
> http://dhis2.org
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+46764147049