Hi, In 2.28. the table "TrackedEntityAttributeReservedValues" is storing unique ID values that have been reserved. When a request is coming from e.g. an Android device running Tracker Capture, the API will trigger the reservation of 100 values and return these to the device while also storing the reserved values in the above table.
Yesterday, I inserted a list of such reserved values into that table in order to "protect" a section of numbers that will be used for importing legacy data. I then decided to verify that those case IDs WERE now actually reserved. 1. when using the normal browser Tracker Capture, it clearly worked - no case IDs coming up were in the reserved range 2. But when I fired up Android Tracker Capture and logged in afresh, the system did reserve 100 more values BUT a number of those were values already in the TrackedEntityAttributeReservedValues table. Or in other words, it seems like a request for reserved values from Tracker Capture via the API will generate reserved values without checking if those values are reserved already - is that correct? Regards Calle -- ******************************************* 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.hedb...@gmail.com Skype: calle_hedberg *******************************************
_______________________________________________ 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
