Compatibility issue between Collect and Aggregate

Support
1

Hi,

I hope I can explain this clearly.

We're using Collect 1.1.7 RC2 with Aggregate 1.0.1 Production. In
our household survey, we designed the form to calculate a
unique number (automatically, on the phone) for each individual child in
the household by creating a id number using a concatenation
of integers entered earlier in the form (interviewer id, cluster id, and
household id) and the child number (1, 2, 3 etc). A relevancy expression in
the child id field should only allow the id number to be generated
if number of children >=1. So, interviewer 1, cluster 5, household 222,
child 1 would generate (and display on the phone) 152221. If
the interviewer specifies that number of children=0, the child id fields
are not relevant, so no id is generated. This works fine with Collect 1.1.7
RC1 and Aggregate Production, but when we installed RC2 on the phones, the
child id is being generated even if there are no children. Although nothing
appears on the phone (as it does if number of children >=1) it DOES appear
on Aggregate. Re-installing RC1 solves the problem.

We could simply use RC1 to avoid the problem, but I thought you might want
to know about it and may have a solution.

Regards,
Glyn

2

the release candidates use different versions of the core, so that
might be the issue. please attach a test form to
http://code.google.com/p/opendatakit/issues/detail?id=456 and i'll
track it down.

ยทยทยท On Wed, Nov 30, 2011 at 01:07, wrote: > Hi, > > I hope I can explain this clearly. > > We're using Collect 1.1.7 RC2 with Aggregate 1.0.1 Production. In > our household survey, we designed the form to calculate a > unique number (automatically, on the phone) for each individual child in the > household by creating a id number using a concatenation of integers entered > earlier in the form (interviewer id, cluster id, and household id) and the > child number (1, 2, 3 etc). A relevancy expression in the child id field > should only allow the id number to be generated if number of children >=1. > So, interviewer 1, cluster 5, household 222, child 1 would generate (and > display on the phone) 152221. If the interviewer specifies that number of > children=0, the child id fields are not relevant, so no id is > generated. This works fine with Collect 1.1.7 RC1 and Aggregate Production, > but when we installed RC2 on the phones, the child id is being generated > even if there are no children. Although nothing appears on the phone (as it > does if number of children >=1) it DOES appear on Aggregate. Re-installing > RC1 solves the problem. > > We could simply use RC1 to avoid the problem, but I thought you might want > to know about it and may have a solution. > > Regards, > Glyn > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en
3

Dear Yaw,

Thanks for offering to look into this. I've downloaded and used the latest
version of Collect and the error does not appear. So, from my end there is
no need to look into this further, but if you want me to attach a sample
form, I will.

Thanks,
Glyn