On my form I have an instance where it makes sense to have multiple
questions per screen. However, I want to have a constraint that
restricts the value of the second field to be greater than or equal to
the value of the first field. (The fields are lower age estimate,
upper age estimate).
The problem is that when there are multiple questions per screen it
doesn't record the answer to any of the questions until you advance to
the next page. As a result, unless you advance and come back after
filling the first question, it will give a constraint error message,
even if the constraint is met.
Does anyone have any suggestions for how this might be fixed?
Otherwise I will have to go back to one question per page...
I am not able to reproduce this problem. I have a test form at http://dpaste.com/709249/ that does what you described and it works
for me on the latest version of Collect.
···
On Mon, Feb 27, 2012 at 02:54, Josephine Walker wrote:
> Hello,
>
> On my form I have an instance where it makes sense to have multiple
> questions per screen. However, I want to have a constraint that
> restricts the value of the second field to be greater than or equal to
> the value of the first field. (The fields are lower age estimate,
> upper age estimate).
>
> The problem is that when there are multiple questions per screen it
> doesn't record the answer to any of the questions until you advance to
> the next page. As a result, unless you advance and come back after
> filling the first question, it will give a constraint error message,
> even if the constraint is met.
>
> Does anyone have any suggestions for how this might be fixed?
> Otherwise I will have to go back to one question per page...
>
> Thanks
> Josephine
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
i have a similar problem with a group of questions on a field-list with a
relevance on the next question.
I have to go back and foward to the collect check the relevance.
i send the xml.
If you put 99 on the first question. Questions number two and number three
have to disapear because they are now irrelevant.
This only happend when you go back and foward. (note that consecuent
questions have to disapear if the previous answer is 99 but this is a work
in progress)
I dont know if this issue is related with the question of josephine but
seems similar to me.
Thanks
I am not able to reproduce this problem. I have a test form at http://dpaste.com/709249/ that does what you described and it works
for me on the latest version of Collect.
On my form I have an instance where it makes sense to have multiple
questions per screen. However, I want to have a constraint that
restricts the value of the second field to be greater than or equal to
the value of the first field. (The fields are lower age estimate,
upper age estimate).
The problem is that when there are multiple questions per screen it
doesn't record the answer to any of the questions until you advance to
the next page. As a result, unless you advance and come back after
filling the first question, it will give a constraint error message,
even if the constraint is met.
Does anyone have any suggestions for how this might be fixed?
Otherwise I will have to go back to one question per page...
Unfortunately, Collect can only check relevance when you advance to the
next screen. You would have to separate the questions into two screens to
get the behavior you want.
i have a similar problem with a group of questions on a field-list with a
relevance on the next question.
I have to go back and foward to the collect check the relevance.
i send the xml.
If you put 99 on the first question. Questions number two and number
three have to disapear because they are now irrelevant.
This only happend when you go back and foward. (note that consecuent
questions have to disapear if the previous answer is 99 but this is a work
in progress)
I dont know if this issue is related with the question of josephine but
seems similar to me.
Thanks
Guillermo A. Perazzo
Josephine,
I am not able to reproduce this problem. I have a test form at http://dpaste.com/709249/ that does what you described and it works
for me on the latest version of Collect.
Take a look at the form above, and if you are still having problems,
please
···
On Thursday, March 1, 2012, Guillermo Perazzo wrote:
> 2012/2/29 Yaw Anokwa
>> file a bug at http://code.google.com/p/opendatakit/issues/list with
>> your form attached.
>>
>> Yaw
>>
>> On Mon, Feb 27, 2012 at 02:54, Josephine Walker wrote:
>> > Hello,
>> >
>> > On my form I have an instance where it makes sense to have multiple
>> > questions per screen. However, I want to have a constraint that
>> > restricts the value of the second field to be greater than or equal to
>> > the value of the first field. (The fields are lower age estimate,
>> > upper age estimate).
>> >
>> > The problem is that when there are multiple questions per screen it
>> > doesn't record the answer to any of the questions until you advance to
>> > the next page. As a result, unless you advance and come back after
>> > filling the first question, it will give a constraint error message,
>> > even if the constraint is met.
>> >
>> > Does anyone have any suggestions for how this might be fixed?
>> > Otherwise I will have to go back to one question per page...
>> >
>> > Thanks
>> > Josephine
>> >
>> > --
>> > 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
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>