Regarding the logic for object matching, it's a bit confusing in the old importer.. it goes something like this
1) Try to match on UID 2) Try to match on CODE 3) If name == unique, match on NAME 4) if object is orgUnit, also try to match on UUID This has changed in the new importer, where we currently only allow matching on UID/CODE, and it has to be explicit (UID is default) -- You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS. https://bugs.launchpad.net/bugs/1614543 Title: Dry run Alters Data 2.23 Status in DHIS: Confirmed Bug description: Hello devs! Just found in 2.23 a bug that will alter metadata during a dry run. Also, if someone come point me at the documentation for the logic for updating existing objects? Right now if a name is the same, it will alter the existing code and uid to the incoming code and uid rather than erroring out, which to me seems like a bad idea to ever edit a UID. You can see an example of this here: The video is in 4k, so if you have trouble seeing it at 1080p, go ahead and download it from this link. https://drive.google.com/file/d/0B9eJ8PZ_4csMd1ZYQnBVb081X1k/view?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/dhis2/+bug/1614543/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp