Currently on 2.16, rev 16408. When registering a new tracked entity with the tracker capture app, I get a message “Error in registering” and see this JSON response (just get an empty “Error in registering” message in the UI")
{"status":"ERROR","importCount":{"imported":0,"updated":0,"ignored":1,"deleted":0},"conflicts":[{"object":"Attribute.value","value":"Value is not boolean for attribute: Attribute{displayName='null', attribute='VGQd25dlkz9', type='null', code='null', value='0'}"}]}
This corresponds to a “Boolean” attribute, so not really sure why it looks like a zero is being sent.
Currently on 2.16, rev 16408. When registering a new tracked entity with the tracker capture app, I get a message “Error in registering” and see this JSON response (just get an empty “Error in registering” message in the UI")
{"status":"ERROR","importCount":{"imported":0,"updated":0,"ignored":1,"deleted":0},"conflicts":[{"object":"Attribute.value","value":"Value is not boolean for attribute: Attribute{displayName='null', attribute='VGQd25dlkz9', type='null', code='null', value='0'}"}]}
This corresponds to a “Boolean” attribute, so not really sure why it looks like a zero is being sent.
One thing which still does not seem to be quite right is the ordering of attributes in the tracker capture app which seem to be not in the same order as in the dhis-web-caseentry module.
One other question as well. We have a requirement to have GPS coordinates as attributes, as we are working with water sources. These coordinates are not ever going to change, so would seem to make sense to have as attributes.
Best regards,
Jason
···
On Sun, Sep 7, 2014 at 10:32 AM, Abyot Gizaw abyota@gmail.com wrote:
Hi Jason,
That was a bug. I just made a fix for both 2.16 and trunk.
Currently on 2.16, rev 16408. When registering a new tracked entity with the tracker capture app, I get a message “Error in registering” and see this JSON response (just get an empty “Error in registering” message in the UI")
{"status":"ERROR","importCount":{"imported":0,"updated":0,"ignored":1,"deleted":0},"conflicts":[{"object":"Attribute.value","value":"Value is not boolean for attribute: Attribute{displayName='null', attribute='VGQd25dlkz9', type='null', code='null', value='0'}"}]}
This corresponds to a “Boolean” attribute, so not really sure why it looks like a zero is being sent.