I followed the approch of overwriting all obsolete values with '0',
which is just as fast as any other update. This works of course only, if
I set zeroIsSigificant to true before overwriting and back to false
before eliminating '0' values - in theory. In praxi, I am able to start
the elimination process in the maintenance app and get a success
message, but the '0' value-records still remain in the dataValues table.
Is there an issue with setting the zeroIsSigificant flag after data were
entered for that dataElement?
By the way: from my experince, bulk deletion by accident is way less
dangerous than randomly changing single values as you can see
immediately that something went wrong :-D (and are able to restore the
backup). If you have processes changing only single values
accidentially, you might find this out only after months - and that's
much harder to correct. It might be worthwhile to rethink this security
feature.
Regards,
Uwe
Am 02.12.2015 um 20:12 schrieb Lars Helge Øverland:
On Wed, Dec 2, 2015 at 6:01 PM, Uwe Wahser <[email protected]
<mailto:[email protected]>> wrote:
That's cheating :-D
True
What do you think of the option of just updating all the obsolete
values to 0 and have them eliminated by DHIS2 (I assume that
0-Values are being eliminated unless I block this in the settings)?
It is a valid approach to generate a data value set filled with blank
values and import it. This will effectively remove the data values.
regards,
Lars
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : [email protected]
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
