dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #52014
Re: DHIS2 2.30 IMPORT/EXPORT ISSUE
Hi,
Your csv file might not import because at least two compulsory fields are
blank:
- Shortname is compulsory (missing)
- Openingdate is compulsory (missing)
I have not tried to import orgunits with those fields missing for a looong
time, but while i seem to recall a missing openingdate would be replaced by
the default date 1970-01-01, I don't think the same happens for shortnames
(note; I could be wrong).
in any case, it's a bad habit to import orgunits with such key fields blank
(for instance, it's unlikely that opening dates from 1970 is anywhere near
the correct openingdates).
Regards
Calle
On Thu, 1 Nov 2018 at 16:43, Kristiyan Panayotov <
Kristiyan@xxxxxxxxxxxxxxxxxxx> wrote:
> Dear Blake,
>
>
>
> Thank you for approaching our issue.
>
>
>
> I am afraid that the solution to the problem is not that simple. DHIS2
> still doesn’t recognize the Org Unit csv file, although that is a structure
> that has been successfully imported in previous versions. I also got the
> parent UID from DHIS2 directly. I have attached the csv in this email, if
> you want to take a look.
>
>
>
> I also send you the screenshot from the failed import (below).
>
>
>
> Thanks,
>
> Kris
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *From:* Blake Hansen [mailto:bhansen@xxxxxxxxxxxxxx]
> *Sent:* Thursday, November 1, 2018 4:23 PM
> *To:* Kristiyan Panayotov <Kristiyan@xxxxxxxxxxxxxxxxxxx>
> *Cc:* dhis2-devs@xxxxxxxxxxxxxxxxxxx; dhis2-users@xxxxxxxxxxxxxxxxxxx;
> Georgi Chakarov <georgi@xxxxxxxxxxxxxxxxxxx>
> *Subject:* Re: [Dhis2-devs] DHIS2 2.30 IMPORT/EXPORT ISSUE
>
>
>
> Hi Kristiyan,
>
>
>
> DHIS2 still support this in 2.30, which you will see in the documentation.
> The only difference is that you no longer have to select the upload file
> type. DHIS2 automatically detects that it is a .csv file. Then you will be
> asked to choose the type of object you are creating.
>
>
>
> So the first step, is click on upload file, select your .csv file, and
> import from there as usual.
>
>
>
> All best,
>
> Blake
>
>
>
>
>
> --
>
>
>
>
>
>
> *Blake Hansen*
> Projects Implementation Manager, BAO Systems
>
> +1 202-536-1541 | bhansen@xxxxxxxxxxxxxx | http://www.baosystems.com |
>
> Skype: blake.a.hansen | 2900 K Street, Suite 507, Washington D.C. 20007
>
>
>
> Register for the 2019 DHIS 2 Symposium:
>
>
> <https://dhis2symposium.org/>
>
>
>
> On 1 Nov 2018, at 11:24, Kristiyan Panayotov <
> Kristiyan@xxxxxxxxxxxxxxxxxxx> wrote:
>
>
>
> Dear DHIS2 experts,
>
>
>
> I am writing to you because I have the following issue with DHIS2 METADATA
> IMPORT:
>
>
>
> I want to import (first) Organizational units and unfortunately I do not
> see the .csv import and object type in the IMPORT/EXPORT APP.
>
>
>
> I see the DHIS2 2.30 guide on importing metadata has this functionalities
> (see below SCREENSHOT 1) that are not present in our DHIS2 instance (see
> below SCREENSHOT 2)
>
>
>
>
>
> My questions, therefore is: How can I import Org Units (and other
> metadata) from a .csv format in DHIS2?
>
>
>
>
>
> Reards,
>
> Kris
>
>
>
>
>
>
> ________________________________________________________________________________
>
> SCREENSHOT 1
>
> <image002.jpg>
>
>
>
>
>
>
>
>
>
> SCREENSHOT 2
>
>
>
>
>
> <image004.jpg>
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>
--
*******************************************
Calle Hedberg
46D Alma Road, 7700 Rosebank, SOUTH AFRICA
Tel/fax (home): +27-21-685-6472
Cell: +27-82-853-5352
Iridium SatPhone: +8816-315-19119
Email: calle.hedberg@xxxxxxxxx
Skype: calle_hedberg
*******************************************
Follow ups
References