I ask people about the number of children in the house and if they say 3,
I need to repeat the question "Age" three times this way without manually adding a group each time:
"Age of 1st Child" - Integer
"Age of 2nd Child" - Integer
"Age of 3rd Child" - Integer
I am familiar with programming but I am new to ODK programming. I am using the XLS template approach as in this page: http://opendatakit.org/use/xlsform/
Looping in ODK is not clear to me. Any help with syntax would be highly appreciated.
Also, can I declare and manipulate any hidden variables in the loop?
If you want to go this route, then you'll need x copies of your age
question, one for each possible age. Say your number-of-children question
is named nchildren. Then say you name your age questions age1, age2, up to
agex. You would set relevance to "${nchildren}>=1" for age1, to
"${nchildren}>=2" for age2, etc., up to agex. It's laborious in the form
design, but it avoids the official looping/repeat-group featureset
altogether. Our surveyors had trouble with the "Do you want to add another
group?" prompts (forever saying yes when they should have said no, or vice
versa), and so we found that asking the number of HH members and then
manually turning on the correct number of follow-up questions worked better.
Best,
Chris
···
On Sunday, March 18, 2012, wrote:
Hello All,
Here is my scenario.
I ask people about the number of children in the house and if they say 3,
I need to repeat the question "Age" three times this way without manually
adding a group each time:
"Age of 1st Child" - Integer
"Age of 2nd Child" - Integer
"Age of 3rd Child" - Integer
I am familiar with programming but I am new to ODK programming. I am using
the XLS template approach as in this page: http://opendatakit.org/use/xlsform/
Looping in ODK is not clear to me. Any help with syntax would be highly
appreciated.
Also, can I declare and manipulate any hidden variables in the loop?
You can have repeats occur n times, where n is a number you entered
earlier. I've put an example at http://pastie.org/3656488. This was a
long standing bug, but I've confirmed that it has been fixed.
···
On Sun, Mar 18, 2012 at 04:12, Christopher Robert wrote:
> Hi Sharada,
>
> If you want to go this route, then you'll need x copies of your age
> question, one for each possible age. Say your number-of-children question is
> named nchildren. Then say you name your age questions age1, age2, up to
> agex. You would set relevance to "${nchildren}>=1" for age1, to
> "${nchildren}>=2" for age2, etc., up to agex. It's laborious in the form
> design, but it avoids the official looping/repeat-group featureset
> altogether. Our surveyors had trouble with the "Do you want to add another
> group?" prompts (forever saying yes when they should have said no, or vice
> versa), and so we found that asking the number of HH members and then
> manually turning on the correct number of follow-up questions worked better.
>
> Best,
>
> Chris
>
>
> On Sunday, March 18, 2012, wrote:
>>
>> Hello All,
>>
>> Here is my scenario.
>>
>> I ask people about the number of children in the house and if they say 3,
>>
>> I need to repeat the question "Age" three times this way without manually
>> adding a group each time:
>>
>> "Age of 1st Child" - Integer
>> "Age of 2nd Child" - Integer
>> "Age of 3rd Child" - Integer
>>
>> I am familiar with programming but I am new to ODK programming. I am using
>> the XLS template approach as in this page:
>> http://opendatakit.org/use/xlsform/
>>
>> Looping in ODK is not clear to me. Any help with syntax would be highly
>> appreciated.
>>
>> Also, can I declare and manipulate any hidden variables in the loop?
>>
>> Thanks in advance.
>>
>> -Sharada
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
Don't think it's progressed further in ODK Collect. ODK Survey (in
alpha now) might be able to support this use case better.
Yaw
···
--
Need ODK help? Go to http://nafundi.com for custom development,
professional support, form design, implementation advice, and user
training for ODK.
In XLSForm, you can add a repeat_count column to the survey sheet, and, on
the row with the "begin repeat", either specify a fixed count or a prior
field like ${fieldname}. That has worked for me.
Best,
Chris
···
On Fri, Feb 15, 2013 at 11:58 AM, dj_bridges wrote:
Yaw,
Has this progressed any further i.e. the number of repeats can be
determined dynamically by a value that the user enters?
Thanks for the replies - will have a look at ODK Survey.
Chris - can't get this to work for me with either a fieldname or a number
to define the number of repeats. When I upload the file to http://opendatakit.org/use/xlsform/ I get a series of error messages.
Removing the repeat number from this column removes all error messages. Any
other ideas?
Keep in mind ODK Survey is in alpha - not at all ready for prime time.
···
On Mon, Feb 18, 2013 at 1:14 AM, dj_bridges wrote:
Thanks for the replies - will have a look at ODK Survey.
Chris - can't get this to work for me with either a fieldname or a number
to define the number of repeats. When I upload the file to http://opendatakit.org/use/xlsform/ I get a series of error messages.
Removing the repeat number from this column removes all error messages. Any
other ideas?
Hi Dan,
You have to reference another field via the ${fieldname} syntax in the
repeat_count column. Unfortunately just putting a number in it doesn't work
at the moment because of an issue with the Javarosa jr:count attribute. I
may eventually add a work around that automatically generates an additional
field from the repeat_count column to avoid the issue.
Regards,
-Nathan
···
On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
>
> Thanks for the replies - will have a look at ODK Survey.
>
> Chris - can't get this to work for me with either a fieldname or a number
> to define the number of repeats. When I upload the file to
> http://opendatakit.org/use/xlsform/ I get a series of error messages.
> Removing the repeat number from this column removes all error messages. Any
> other ideas?
>
Did this jr:count problem just come up recently? I could swear that I just
tested it last week, and it worked fine for me -- though my build is from
sources that are roughly 4-6 months old.
Thanks,
Chris
···
On Tuesday, February 19, 2013, Nathan wrote:
Hi Dan,
You have to reference another field via the ${fieldname} syntax in the
repeat_count column. Unfortunately just putting a number in it doesn't work
at the moment because of an issue with the Javarosa jr:count attribute. I
may eventually add a work around that automatically generates an additional
field from the repeat_count column to avoid the issue.
Regards,
-Nathan
On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
Thanks for the replies - will have a look at ODK Survey.
Chris - can't get this to work for me with either a fieldname or a number
to define the number of repeats. When I upload the file to http://opendatakit.org/use/**xlsform/http://opendatakit.org/use/xlsform/I get a series of error messages. Removing the repeat number from this
column removes all error messages. Any other ideas?
You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com <javascript:_e({},
'cvml', 'opendatakit%2Bunsubscribe@googlegroups.com');>.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Chris,
I would be surprised if it worked before. It is possible that the error
wasn't being picked up by the XLSForm converter before, or by your build of
it. The error comes after the XML is generated when it is checked by ODK
Validate.
Regards,
-Nathan
···
On Monday, February 18, 2013 7:56:14 PM UTC-8, Chris wrote:
>
> Hi Nathan,
>
> Did this jr:count problem just come up recently? I could swear that I just
> tested it last week, and it worked fine for me -- though my build is from
> sources that are roughly 4-6 months old.
>
> Thanks,
>
> Chris
>
> On Tuesday, February 19, 2013, Nathan wrote:
>
>> Hi Dan,
>> You have to reference another field via the ${fieldname} syntax in the
>> repeat_count column. Unfortunately just putting a number in it doesn't work
>> at the moment because of an issue with the Javarosa jr:count attribute. I
>> may eventually add a work around that automatically generates an additional
>> field from the repeat_count column to avoid the issue.
>> Regards,
>> -Nathan
>>
>> On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
>>>
>>> Thanks for the replies - will have a look at ODK Survey.
>>>
>>> Chris - can't get this to work for me with either a fieldname or a
>>> number to define the number of repeats. When I upload the file to
>>> http://opendatakit.org/use/**xlsform/I get a series of error messages. Removing the repeat number from this
>>> column removes all error messages. Any other ideas?
>>>
>> --
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
You were totally right. I was certain that I'd tested the fixed-count case,
but clearly I hadn't. Weird.
I have revised my documentation accordingly. If any customers bother me
about it, maybe I'll research and submit a fix.
Best,
Chris
···
On Tue, Feb 19, 2013 at 7:08 PM, Nathan wrote:
Hi Chris,
I would be surprised if it worked before. It is possible that the error
wasn't being picked up by the XLSForm converter before, or by your build of
it. The error comes after the XML is generated when it is checked by ODK
Validate.
Regards,
-Nathan
On Monday, February 18, 2013 7:56:14 PM UTC-8, Chris wrote:
Hi Nathan,
Did this jr:count problem just come up recently? I could swear that I
just tested it last week, and it worked fine for me -- though my build is
from sources that are roughly 4-6 months old.
Thanks,
Chris
On Tuesday, February 19, 2013, Nathan wrote:
Hi Dan,
You have to reference another field via the ${fieldname} syntax in the
repeat_count column. Unfortunately just putting a number in it doesn't work
at the moment because of an issue with the Javarosa jr:count attribute. I
may eventually add a work around that automatically generates an additional
field from the repeat_count column to avoid the issue.
Regards,
-Nathan
On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
Thanks for the replies - will have a look at ODK Survey.
Chris - can't get this to work for me with either a fieldname or a
number to define the number of repeats. When I upload the file to http://opendatakit.org/use/****xlsform/http://opendatakit.org/use/xlsform/I get a series of error messages. Removing the repeat number from this
column removes all error messages. Any other ideas?
Hi Chris,
I recently added the work-around I mentioned above to the opendatakit.org
XLSForm converter, so using fixed counts or formulas in the choice_filter
column should no longer be an issue.
Regards,
-Nathan
···
On Tuesday, February 26, 2013 12:14:45 AM UTC-8, Chris wrote:
>
> Hi Nathan,
>
> You were totally right. I was certain that I'd tested the fixed-count
> case, but clearly I hadn't. Weird.
>
> I have revised my documentation accordingly. If any customers bother me
> about it, maybe I'll research and submit a fix.
>
> Best,
>
> Chris
>
>
>
> On Tue, Feb 19, 2013 at 7:08 PM, Nathan <nab...@gmail.com >wrote:
>
>> Hi Chris,
>> I would be surprised if it worked before. It is possible that the error
>> wasn't being picked up by the XLSForm converter before, or by your build of
>> it. The error comes after the XML is generated when it is checked by ODK
>> Validate.
>> Regards,
>> -Nathan
>>
>>
>> On Monday, February 18, 2013 7:56:14 PM UTC-8, Chris wrote:
>>>
>>> Hi Nathan,
>>>
>>> Did this jr:count problem just come up recently? I could swear that I
>>> just tested it last week, and it worked fine for me -- though my build is
>>> from sources that are roughly 4-6 months old.
>>>
>>> Thanks,
>>>
>>> Chris
>>>
>>> On Tuesday, February 19, 2013, Nathan wrote:
>>>
>>>> Hi Dan,
>>>> You have to reference another field via the ${fieldname} syntax in the
>>>> repeat_count column. Unfortunately just putting a number in it doesn't work
>>>> at the moment because of an issue with the Javarosa jr:count attribute. I
>>>> may eventually add a work around that automatically generates an additional
>>>> field from the repeat_count column to avoid the issue.
>>>> Regards,
>>>> -Nathan
>>>>
>>>> On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
>>>>>
>>>>> Thanks for the replies - will have a look at ODK Survey.
>>>>>
>>>>> Chris - can't get this to work for me with either a fieldname or a
>>>>> number to define the number of repeats. When I upload the file to
>>>>> http://opendatakit.org/use/****xlsform/I get a series of error messages. Removing the repeat number from this
>>>>> column removes all error messages. Any other ideas?
>>>>>
>>>> --
>>>> --
>>>> Post: opendatakit@googlegroups.com
>>>> Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> Options: http://groups.google.com/**group/opendatakit?hl=en
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "ODK Community" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to opendatakit+unsubscribe@**googlegroups.com.
>>>> For more options, visit https://groups.google.com/**groups/opt_out
>>>> .
>>>>
>>>>
>>>>
>>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
I've done a lot of testing, a lot of documenting, and a little extending
based on the 9/3/2012 pyxform repo; I've got a handful of project sites
working happily with bunches of working .xls forms; and I'm a few weeks
away from a long-awaited public release of a packaged/supported/integrated
ODK for the masses (sort of).
For a while now, I've had on my to-do list to go back to pyxform and track
what you guys have been up to. Now that I've done that, I see that you've
done quite a lot since Sep. 3!
I don't know that I'd want to make wholesale changes so close to release,
but out of curiosity: is it your opinion that, if I merged in your post-9/3
changes, there would be no backward-compatibility issues? Or are there
likely to be things like the lowercased column headings?
I'm also curious how close you are to what you'd consider a v1.0 release,
because I see that you have been asymptotically approaching v1.0 with your
version numbers.
Thanks,
Chris
···
On Tue, Feb 26, 2013 at 7:19 PM, Nathan wrote:
Hi Chris,
I recently added the work-around I mentioned above to the opendatakit.orgXLSForm converter, so using fixed counts or formulas in the choice_filter
column should no longer be an issue.
Regards,
-Nathan
On Tuesday, February 26, 2013 12:14:45 AM UTC-8, Chris wrote:
Hi Nathan,
You were totally right. I was certain that I'd tested the fixed-count
case, but clearly I hadn't. Weird.
I have revised my documentation accordingly. If any customers bother me
about it, maybe I'll research and submit a fix.
Hi Chris,
I would be surprised if it worked before. It is possible that the error
wasn't being picked up by the XLSForm converter before, or by your build of
it. The error comes after the XML is generated when it is checked by ODK
Validate.
Regards,
-Nathan
On Monday, February 18, 2013 7:56:14 PM UTC-8, Chris wrote:
Hi Nathan,
Did this jr:count problem just come up recently? I could swear that I
just tested it last week, and it worked fine for me -- though my build is
from sources that are roughly 4-6 months old.
Thanks,
Chris
On Tuesday, February 19, 2013, Nathan wrote:
Hi Dan,
You have to reference another field via the ${fieldname} syntax in the
repeat_count column. Unfortunately just putting a number in it doesn't work
at the moment because of an issue with the Javarosa jr:count attribute. I
may eventually add a work around that automatically generates an additional
field from the repeat_count column to avoid the issue.
Regards,
-Nathan
On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
Thanks for the replies - will have a look at ODK Survey.
Chris - can't get this to work for me with either a fieldname or a
number to define the number of repeats. When I upload the file to http://opendatakit.org/use/******xlsform/http://opendatakit.org/use/xlsform/I get a series of error messages. Removing the repeat number from this
column removes all error messages. Any other ideas?
You received this message because you are subscribed to the Google
Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit...@**googlegroups.com.
I don't think you'd run into backwards compatibility issues, but it's hard
to be certain.
Instance IDs are added to all forms now and that might be an issue if you
are using an older (pre 1.1.7) version of Collect.
I think the trade-off boils down to this:
The newer version doesn't have have any known problems, but is more likely
to have unknown problems.
The older version has some known problems, but since you've been using it
for a while, it is less likely to have unknown problems.
We don't have plans for a 1.0 release, although I suppose we could call the
next version 1.0.
There isn't a road map, so it wouldn't really mean anything. Essentially I
just try to fix bugs and add features as they are reported/requested.
Regards,
-Nathan
···
On Wednesday, February 27, 2013 8:40:52 AM UTC-8, Chris wrote:
>
> Hi Nathan,
>
> Thanks.
>
> I've done a lot of testing, a lot of documenting, and a little extending
> based on the 9/3/2012 pyxform repo; I've got a handful of project sites
> working happily with bunches of working .xls forms; and I'm a few weeks
> away from a long-awaited public release of a packaged/supported/integrated
> ODK for the masses (sort of).
>
> For a while now, I've had on my to-do list to go back to pyxform and track
> what you guys have been up to. Now that I've done that, I see that you've
> done quite a lot since Sep. 3!
>
> I don't know that I'd want to make wholesale changes so close to release,
> but out of curiosity: is it your opinion that, if I merged in your post-9/3
> changes, there would be no backward-compatibility issues? Or are there
> likely to be things like the lowercased column headings?
>
> I'm also curious how close you are to what you'd consider a v1.0 release,
> because I see that you have been asymptotically approaching v1.0 with your
> version numbers.
>
> Thanks,
>
> Chris
>
>
>
> On Tue, Feb 26, 2013 at 7:19 PM, Nathan <nab...@gmail.com >wrote:
>
>> Hi Chris,
>> I recently added the work-around I mentioned above to the opendatakit.orgXLSForm converter, so using fixed counts or formulas in the choice_filter
>> column should no longer be an issue.
>> Regards,
>> -Nathan
>>
>>
>> On Tuesday, February 26, 2013 12:14:45 AM UTC-8, Chris wrote:
>>
>>> Hi Nathan,
>>>
>>> You were totally right. I was certain that I'd tested the fixed-count
>>> case, but clearly I hadn't. Weird.
>>>
>>> I have revised my documentation accordingly. If any customers bother me
>>> about it, maybe I'll research and submit a fix.
>>>
>>> Best,
>>>
>>> Chris
>>>
>>>
>>>
>>> On Tue, Feb 19, 2013 at 7:08 PM, Nathan wrote:
>>>
>>>> Hi Chris,
>>>> I would be surprised if it worked before. It is possible that the error
>>>> wasn't being picked up by the XLSForm converter before, or by your build of
>>>> it. The error comes after the XML is generated when it is checked by ODK
>>>> Validate.
>>>> Regards,
>>>> -Nathan
>>>>
>>>>
>>>> On Monday, February 18, 2013 7:56:14 PM UTC-8, Chris wrote:
>>>>>
>>>>> Hi Nathan,
>>>>>
>>>>> Did this jr:count problem just come up recently? I could swear that I
>>>>> just tested it last week, and it worked fine for me -- though my build is
>>>>> from sources that are roughly 4-6 months old.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Chris
>>>>>
>>>>> On Tuesday, February 19, 2013, Nathan wrote:
>>>>>
>>>>>> Hi Dan,
>>>>>> You have to reference another field via the ${fieldname} syntax in
>>>>>> the repeat_count column. Unfortunately just putting a number in it doesn't
>>>>>> work at the moment because of an issue with the Javarosa jr:count
>>>>>> attribute. I may eventually add a work around that automatically generates
>>>>>> an additional field from the repeat_count column to avoid the issue.
>>>>>> Regards,
>>>>>> -Nathan
>>>>>>
>>>>>> On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
>>>>>>>
>>>>>>> Thanks for the replies - will have a look at ODK Survey.
>>>>>>>
>>>>>>> Chris - can't get this to work for me with either a fieldname or a
>>>>>>> number to define the number of repeats. When I upload the file to
>>>>>>> http://opendatakit.org/use/******xlsform/I get a series of error messages. Removing the repeat number from this
>>>>>>> column removes all error messages. Any other ideas?
>>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Post: opendatakit@googlegroups.com
>>>>>> Unsubscribe: opendatakit+unsubscribe@**google**groups.com
>>>>>> Options: http://groups.google.com/**group**/opendatakit?hl=en
>>>>>>
>>>>>> ---
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "ODK Community" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to opendatakit+unsubscribe@**google**groups.com.
>>>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out
>>>>>> .
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>> --
>>>> Post: opend...@googlegroups.com
>>>> Unsubscribe: opendatakit...@**googlegroups.com
>>>>
>>>> Options: http://groups.google.com/**group/opendatakit?hl=en
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "ODK Community" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to opendatakit...@**googlegroups.com.
>>>>
>>>> For more options, visit https://groups.google.com/**groups/opt_out
>>>> .
>>>>
>>>>
>>>>
>>>
>>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
It's always difficult to know whether to stick with known unknowns or go
with unknown unknowns. I'll try to come up with my own roadmap that deals
with upgrades in a safe, sensible way. Probably I'll wait till after the
initial release to upgrade anything.
Thanks again,
Chris
···
On Wed, Feb 27, 2013 at 8:30 PM, Nathan wrote:
Hi Chris,
I don't think you'd run into backwards compatibility issues, but it's hard
to be certain.
Instance IDs are added to all forms now and that might be an issue if you
are using an older (pre 1.1.7) version of Collect.
I think the trade-off boils down to this:
The newer version doesn't have have any known problems, but is more likely
to have unknown problems.
The older version has some known problems, but since you've been using it
for a while, it is less likely to have unknown problems.
We don't have plans for a 1.0 release, although I suppose we could call
the next version 1.0.
There isn't a road map, so it wouldn't really mean anything. Essentially
I just try to fix bugs and add features as they are reported/requested.
Regards,
-Nathan
On Wednesday, February 27, 2013 8:40:52 AM UTC-8, Chris wrote:
Hi Nathan,
Thanks.
I've done a lot of testing, a lot of documenting, and a little extending
based on the 9/3/2012 pyxform repo; I've got a handful of project sites
working happily with bunches of working .xls forms; and I'm a few weeks
away from a long-awaited public release of a packaged/supported/integrated
ODK for the masses (sort of).
For a while now, I've had on my to-do list to go back to pyxform and
track what you guys have been up to. Now that I've done that, I see that
you've done quite a lot since Sep. 3!
I don't know that I'd want to make wholesale changes so close to release,
but out of curiosity: is it your opinion that, if I merged in your post-9/3
changes, there would be no backward-compatibility issues? Or are there
likely to be things like the lowercased column headings?
I'm also curious how close you are to what you'd consider a v1.0 release,
because I see that you have been asymptotically approaching v1.0 with your
version numbers.
Hi Chris,
I recently added the work-around I mentioned above to the opendatakit.org XLSForm converter, so using fixed counts or formulas in
the choice_filter column should no longer be an issue.
Regards,
-Nathan
On Tuesday, February 26, 2013 12:14:45 AM UTC-8, Chris wrote:
Hi Nathan,
You were totally right. I was certain that I'd tested the fixed-count
case, but clearly I hadn't. Weird.
I have revised my documentation accordingly. If any customers bother me
about it, maybe I'll research and submit a fix.
Hi Chris,
I would be surprised if it worked before. It is possible that the
error wasn't being picked up by the XLSForm converter before, or by your
build of it. The error comes after the XML is generated when it is checked
by ODK Validate.
Regards,
-Nathan
On Monday, February 18, 2013 7:56:14 PM UTC-8, Chris wrote:
Hi Nathan,
Did this jr:count problem just come up recently? I could swear that I
just tested it last week, and it worked fine for me -- though my build is
from sources that are roughly 4-6 months old.
Thanks,
Chris
On Tuesday, February 19, 2013, Nathan wrote:
Hi Dan,
You have to reference another field via the ${fieldname} syntax in
the repeat_count column. Unfortunately just putting a number in it doesn't
work at the moment because of an issue with the Javarosa jr:count
attribute. I may eventually add a work around that automatically generates
an additional field from the repeat_count column to avoid the issue.
Regards,
-Nathan
On Monday, February 18, 2013 1:14:50 AM UTC-8, dj_bridges wrote:
Thanks for the replies - will have a look at ODK Survey.
Chris - can't get this to work for me with either a fieldname or a
number to define the number of repeats. When I upload the file to http://opendatakit.org/use/********xlsform/http://opendatakit.org/use/xlsform/I get a series of error messages. Removing the repeat number from this
column removes all error messages. Any other ideas?
You received this message because you are subscribed to the Google
Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to opendatakit+unsubscribe@**googlegroups.com.
For more options, visit https://groups.google.com/**grou
ps/opt_out https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google
Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit...@**googlegroups.**com.