If my answer to is N (for No), then I want to skip
everything to do with the group/repeating node. Unfortunately, I can't
get the relevancy to work.
No matter where I put the relevant attribute, Collect prompts me to
"Add another 'Group to Repeat' group?" if I answer No to the
branchquestion.
The incarnation below has the relevance on both the group node and a
question node in the group. I've tried just on the group node, and
just on the question node, to no avail.
all these repeat relevancy bugs have been fixed in javarosa. have they yet
to be migrated to ODK?
stuart, you might have better luck containing inside a group
itself (just in the instance, not a literal ), then setting the
relevancy condition only on that top group node.
If my answer to is N (for No), then I want to skip
everything to do with the group/repeating node. Unfortunately, I can't
get the relevancy to work.
No matter where I put the relevant attribute, Collect prompts me to
"Add another 'Group to Repeat' group?" if I answer No to the
branchquestion.
The incarnation below has the relevance on both the group node and a
question node in the group. I've tried just on the group node, and
just on the question node, to no avail.
the next release of collect will have the new core moved over.
···
On Wed, Feb 9, 2011 at 11:52, Stuart Moffatt wrote:
> Work around was just right -- issue solved.
> Thanks Drew.
>
>
> On Wed, Feb 9, 2011 at 12:45 PM, Stuart Moffatt wrote:
>>
>> Thanks Drew -- will give your workaround a shot
>>
>>
>> On Wed, Feb 9, 2011 at 12:43 PM, Drew Roos wrote:
>>>
>>> all these repeat relevancy bugs have been fixed in javarosa. have they
>>> yet to be migrated to ODK?
>>>
>>> stuart, you might have better luck containing inside a
>>> group itself (just in the instance, not a literal ), then setting the
>>> relevancy condition only on that top group node.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> >> type="string"/>
>>>>
>>>>
>>>> Do we need to branch?
>>>> YesY
>>>> NoN
>>>>
>>>
>>>
>>>>
>>>>
>>>> Group To Repeat
>>>>
>>>>
>>>> One
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> On Wed, Feb 9, 2011 at 2:35 PM, Stuart Moffatt wrote:
>>>>
>>>> If my answer to is N (for No), then I want to skip
>>>> everything to do with the group/repeating node. Unfortunately, I can't
>>>> get the relevancy to work.
>>>>
>>>> No matter where I put the relevant attribute, Collect prompts me to
>>>> "Add another 'Group to Repeat' group?" if I answer No to the
>>>> branchquestion.
>>>>
>>>> The incarnation below has the relevance on both the group node and a
>>>> question node in the group. I've tried just on the group node, and
>>>> just on the question node, to no avail.
>>>>
>>>> What am I doing incorrectly?
>>>>
>>>> <?xml version="1.0"?>
>>>> >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jr="http://
>>>> openrosa.org/javarosa">
>>>>
>>>> GRC 002
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> >>> relevant="selected(/grc/branchquestion, 'Y')"/>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Do we need to branch?
>>>> YesY
>>>> NoN
>>>>
>>>>
>>>> Group To Repeat
>>>>
>>>>
>>>> One
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>
···
On Wed, Feb 9, 2011 at 12:43 PM, Drew Roos wrote:
all these repeat relevancy bugs have been fixed in javarosa. have they yet
to be migrated to ODK?
stuart, you might have better luck containing inside a
group itself (just in the instance, not a literal ), then setting the
relevancy condition only on that top group node.
If my answer to is N (for No), then I want to skip
everything to do with the group/repeating node. Unfortunately, I can't
get the relevancy to work.
No matter where I put the relevant attribute, Collect prompts me to
"Add another 'Group to Repeat' group?" if I answer No to the
branchquestion.
The incarnation below has the relevance on both the group node and a
question node in the group. I've tried just on the group node, and
just on the question node, to no avail.
···
On Wed, Feb 9, 2011 at 12:45 PM, Stuart Moffatt wrote:
Thanks Drew -- will give your workaround a shot
On Wed, Feb 9, 2011 at 12:43 PM, Drew Roos droos@dimagi.com wrote:
all these repeat relevancy bugs have been fixed in javarosa. have they yet
to be migrated to ODK?
stuart, you might have better luck containing inside a
group itself (just in the instance, not a literal ), then setting the
relevancy condition only on that top group node.
If my answer to is N (for No), then I want to skip
everything to do with the group/repeating node. Unfortunately, I can't
get the relevancy to work.
No matter where I put the relevant attribute, Collect prompts me to
"Add another 'Group to Repeat' group?" if I answer No to the
branchquestion.
The incarnation below has the relevance on both the group node and a
question node in the group. I've tried just on the group node, and
just on the question node, to no avail.
If my answer to is N (for No), then I want to skip
everything to do with the group/repeating node. Unfortunately, I can't
get the relevancy to work.
No matter where I put the relevant attribute, Collect prompts me to
"Add another 'Group to Repeat' group?" if I answer No to the
branchquestion.
The incarnation below has the relevance on both the group node and a
question node in the group. I've tried just on the group node, and
just on the question node, to no avail.