-
```
Current behaviour is to append a number to the form name to distinguish it from
the existing form. We find that the existence of two forms with the same name
confuses most enumerators, and that …
-
```
Current behaviour is to append a number to the form name to distinguish it from
the existing form. We find that the existence of two forms with the same name
confuses most enumerators, and that …
-
```
Currently, when responses are submitted, the data still remains available on
the phone and must be manually deleted using the file management interface of
ODK.
We find that enumerators will not…
-
```
Current behaviour is to append a number to the form name to distinguish it from
the existing form. We find that the existence of two forms with the same name
confuses most enumerators, and that …
-
```
Currently, when responses are submitted, the data still remains available on
the phone and must be manually deleted using the file management interface of
ODK.
We find that enumerators will not…
-
```
Current behaviour is to append a number to the form name to distinguish it from
the existing form. We find that the existence of two forms with the same name
confuses most enumerators, and that …
-
```
Forms can be deleted from the form management interface even if there is some
saved and unsubmitted data for the form. When this happens, attempts to review
the data cause an exception and cause…
-
```
Forms can be deleted from the form management interface even if there is some
saved and unsubmitted data for the form. When this happens, attempts to review
the data cause an exception and cause…
-
```
Forms can be deleted from the form management interface even if there is some
saved and unsubmitted data for the form. When this happens, attempts to review
the data cause an exception and cause…
-
Originally reported on Google Code with ID 386
```
"Hello ODK,
attached is a survey designed using purcforms. I ran it on ODK Collect 1.5 and got
some strange behaviour. It loads fine but when you …