This is a major issue in our case. We are going live in a week. In our situation for house hold surveys. We are interviewing house members in repeat groups inside the main household survey. If a certain member of household is not present we save the survey and move on to the next house to come and interview the missing household member at a later time(Using Edit Saved Forms function on ODK). We cannot accomplish this because of the error around multiple instances of the same form.
And btw I am using the form ID to identify the form.
Is there a workaround to this issue? The solution above does not work for us as we have many(30+) devices; changing and muddling with forms.db is a big headache.
We don't have a fix to correct existing errors.
If you need the fix that will prevent this going forward, the latest "ODK
Collect 1.2 RC1 - 1008" has it.
This is not our official release (which is still 1.1.7), but should be
quite stable.
"RC1" stands for Release Candidate #1, which implies less stability than an
official release.
This release is only available from our developer site:
This is a major issue in our case. We are going live in a week. In our situation for house hold surveys. We are interviewing house members in repeat groups inside the main household survey. If a certain member of household is not present we save the survey and move on to the next house to come and interview the missing household member at a later time(Using Edit Saved Forms function on ODK). We cannot accomplish this because of the error around multiple instances of the same form.
And btw I am using the form ID to identify the form.
Is there a workaround to this issue? The solution above does not work for us as we have many(30+) devices; changing and muddling with forms.db is a big headache.
Whoa!!!!! , Thanks Mitch for creating a RC release.
This helps a lot(by leaps and bounds).
Regards
R
···
On Friday, May 25, 2012 1:43:53 PM UTC-4, Mitch wrote:
>
> We don't have a fix to correct existing errors.
> If you need the fix that will prevent this going forward, the latest "ODK
> Collect 1.2 RC1 - 1008" has it.
>
> *This is not our official release* (which is still 1.1.7), but should be
> quite stable.
> "RC1" stands for Release Candidate #1, which implies less stability than
> an official release.
>
> This release is only available from our developer site:
>
> http://code.google.com/p/opendatakit/downloads/list
>
> Mitch
>
>
> On Fri, May 25, 2012 at 5:52 AM, arbor wrote:
>
>>
>> Working with Multiple instances of the same form.When we try to "Edit Saved Form" it throws an error "More than one possible parent form".
>>
>> There has been an issue identified (see link below)
>>
>>
>> http://code.google.com/p/opendatakit/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&groupby=&sort=&id=579
>>
>>
>>
>> This is a major issue in our case. We are going live in a week. In our situation for house hold surveys. We are interviewing house members in repeat groups inside the main household survey. If a certain member of household is not present we save the survey and move on to the next house to come and interview the missing household member at a later time(Using Edit Saved Forms function on ODK). We cannot accomplish this because of the error around multiple instances of the same form.
>>
>>
>> And btw I am using the form ID to identify the form.
>>
>> Is there a workaround to this issue? The solution above does not work for us as we have many(30+) devices; changing and muddling with forms.db is a big headache.
>>
>> Any help or suggestions will be help ful.
>>
>>
>> Regards
>>
>> R
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>
On Friday, May 25, 2012 1:43:53 PM UTC-4, Mitch wrote:
We don't have a fix to correct existing errors.
If you need the fix that will prevent this going forward, the latest "ODK
Collect 1.2 RC1 - 1008" has it.
This is not our official release (which is still 1.1.7), but should be
quite stable.
"RC1" stands for Release Candidate #1, which implies less stability than
an official release.
This release is only available from our developer site:
This is a major issue in our case. We are going live in a week. In our situation for house hold surveys. We are interviewing house members in repeat groups inside the main household survey. If a certain member of household is not present we save the survey and move on to the next house to come and interview the missing household member at a later time(Using Edit Saved Forms function on ODK). We cannot accomplish this because of the error around multiple instances of the same form.
And btw I am using the form ID to identify the form.
Is there a workaround to this issue? The solution above does not work for us as we have many(30+) devices; changing and muddling with forms.db is a big headache.
On Friday, May 25, 2012 1:43:53 PM UTC-4, Mitch wrote:
We don't have a fix to correct existing errors.
If you need the fix that will prevent this going forward, the latest "ODK
Collect 1.2 RC1 - 1008" has it.
This is not our official release (which is still 1.1.7), but should be
quite stable.
"RC1" stands for Release Candidate #1, which implies less stability than
an official release.
This release is only available from our developer site:
This is a major issue in our case. We are going live in a week. In our situation for house hold surveys. We are interviewing house members in repeat groups inside the main household survey. If a certain member of household is not present we save the survey and move on to the next house to come and interview the missing household member at a later time(Using Edit Saved Forms function on ODK). We cannot accomplish this because of the error around multiple instances of the same form.
And btw I am using the form ID to identify the form.
Is there a workaround to this issue? The solution above does not work for us as we have many(30+) devices; changing and muddling with forms.db is a big headache.