The data entry started well. In the first month there were 6 rain days. The total was given as 33.3mm.
However the total (or one of the values) was incorrect. It was actually 34.3mm. So the save correctly didn't work.
But the message was misleading. It says the computed total was 34. Well it sort of was, but it should have said 34.3, i.e. it is probably set to give an integer value, but should be fixed, so it gives a decimal.
I entered precipitation data for January 2016 and clicked Save. I turned off the element sequencer, because I just have precipitation. I then did Add New and nothing happened. I expected to get a new blank record for the next month. Instead the same January record remains, though Add New is now disabled. I now understand I need to change the month to 2 for February. I wonder why it can't have a month sequencer for rainfall data entry? That would be safer.
@rdstern thanks for reporting your observations in course of the testing exercise. @mhabimana may try and compile all the issues reported indicating which fall under AMI and those under me.
The data entry started well. In the first month there were 6 rain days. The total was given as 33.3mm.
However the total (or one of the values) was incorrect. It was actually 34.3mm. So the save correctly didn't work. But the message was misleading. It says the computed total was 34. Well it sort of was, but it should have said 34.3, i.e. it is probably set to give an integer value, but should be fixed, so it gives a decimal.
I entered precipitation data for January 2016 and clicked Save. I turned off the element sequencer, because I just have precipitation. I then did Add New and nothing happened. I expected to get a new blank record for the next month. Instead the same January record remains, though Add New is now disabled. I now understand I need to change the month to 2 for February. I wonder why it can't have a month sequencer for rainfall data entry? That would be safer.