We don't currently support mixed dynamic/static selection in our itemsets
and to be quite honest it had never occurred to me whether the spec allows
for it. A quick read doesn't actually seem to clarify for me whether it's
valid so I'll have to dig a bit deeper. Internally it'll be a big lift to
make that output mixed, though, so unfortunately I think it's not something
we can turnaround in the short-term.
-Clayton
···
On Fri, Oct 16, 2015 at 2:00 AM, Ray Brunsting wrote:
We'd like to include both items and itemsets in a single select question,
and am seeing the following build error. Is there a workaround? Thanks,
Ray
FYI. Refactoring to use two itemsets eliminated the build error, however,i
it looks like only items from the second itemset are shown to the end-user.
Ray
···
On Friday, October 16, 2015 at 1:47:23 AM UTC-4, Clayton Sims wrote:
>
> Ray,
>
> We don't currently support mixed dynamic/static selection in our itemsets
> and to be quite honest it had never occurred to me whether the spec allows
> for it. A quick read doesn't actually seem to clarify for me whether it's
> valid so I'll have to dig a bit deeper. Internally it'll be a big lift to
> make that output mixed, though, so unfortunately I think it's not something
> we can turnaround in the short-term.
>
> -Clayton
>
> On Fri, Oct 16, 2015 at 2:00 AM, Ray Brunsting <r...@tula.org > wrote:
>
>> We'd like to include both items and itemsets in a single select question,
>> and am seeing the following build error. Is there a workaround? Thanks,
>> Ray
>>
>>
>> Build Failed!
>>
>> - Validation Error: Multiple choice question contains both literal
>> choices and in form Crear Embarazo
>> in
>> module "Crear Embarazo"
>>
>> For more information on build errors, please see Errors Building an
>> Application
>>
>>
>>
>>
>> *Our xform:*
>>
>>
>>
>>
>>
>> null_item
>>
>> > nodeset="instance('casedb')/casedb/case[@case_type='comunidad'][@status='open']">
>>
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "commcare-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to commcare-user...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
Yeah, I anticipate that it's simply overriding the original definition.
Technically it would definitely be easier for us to merge itemsets than mix
and declarations, but I'd still need to check that that is
OK with the spec before doing so.
-Clayton
···
On Fri, Oct 16, 2015 at 5:37 PM, Ray Brunsting wrote:
FYI. Refactoring to use two itemsets eliminated the build error,
however,i it looks like only items from the second itemset are shown to the
end-user. Ray
On Friday, October 16, 2015 at 1:47:23 AM UTC-4, Clayton Sims wrote:
Ray,
We don't currently support mixed dynamic/static selection in our itemsets
and to be quite honest it had never occurred to me whether the spec allows
for it. A quick read doesn't actually seem to clarify for me whether it's
valid so I'll have to dig a bit deeper. Internally it'll be a big lift to
make that output mixed, though, so unfortunately I think it's not something
we can turnaround in the short-term.
-Clayton
On Fri, Oct 16, 2015 at 2:00 AM, Ray Brunsting r...@tula.org wrote:
We'd like to include both items and itemsets in a single select
question, and am seeing the following build error. Is there a workaround?
Thanks, Ray
--
You received this message because you are subscribed to the Google
Groups "commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.