This is most likely an (unintended) consequence of the somewhat
contrived method we're using to import coordinates from GML files.
Unfortunately it's most likely not an easy fix, but I'll look into it.
Does this issue have any immediate consequences for your
implementation(s)?
Thanks for reporting!
** Changed in: dhis2
Status: New => Confirmed
** Changed in: dhis2
Assignee: (unassigned) => Halvdan Hoem Grelland (halvdanhg)
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1597724
Title:
Import of GML file update lastupdated date of all objects with co-
ordinates
Status in DHIS:
Confirmed
Bug description:
Importing of a GML file updates the "lastupdated" date of all
organisationunit with GIS co-ordinates to the date of the import.
Not sure if this is by design but it creates a problem for facility
registries in that it appears that all organisationunits with co-
ordinates had some field updated every time a GML file is imported
when in fact only some of the objects had updates.
Ideally the import should only update new/real updates and for those
update the GIS co-ordinates instead of overwriting all co-ordinates
and seeing them as updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1597724/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
