Bug with repeat aggregate function?

Question

Hi,  I have a survey which uses repeats, and sums the total within each repeat using the aggregate function e.g. sum(${repeat_value}).

Since upgrading to Survey123 version 2.7.98 (and Survey123 Connect 2.7.72) this no longer works - the entry box remains blank.  This worked perfectly in the previous version.

Is this a bug, or has the syntax changed somehow?

Thanks!

ClaireMWood · Answer

Hi James Tedrick‌

I have recently updated to Connect version 3.7.62 and am getting this same problem again and the changes I made in the previous post are no longer working.

So to summarize, my survey uses repeats, and sums the total within each repeat using the aggregate function e.g. sum(${repeat_value}).  Each of these totals is summed in a single calculation e.g.   sum(${repeat_value1})+sum(${repeat_value2})+sum(${repeat_value3}).  This used to work, but now doesn't.

Hope you can help!

Claire

DaveKerr1 · Answer

I have been trying to do this without luck, just came across this and will try it.

Is there any way we can get this to work with Decimals? We enter partial values, can't have them truncated.

ClaireMWood · Answer

Hi,

I’ve figured out what the problem is.  In order to use the aggregate function, sum(${repeat_value}), the values in the repeat had to be converted to integers in separate fields using ‘number(${field})’.  These new columns were hidden using a ‘relevant’ clause.  However, this no longer works as the calculation no longer was being evaluated where the column is not relevant.

I have changed these hidden fields to ‘hidden’ types, removed the ‘relevant’ clause, added ind:esriFieldType as esriFieldTypeInteger and added a column called ‘bind::type’ and set to ‘int’.   This now appears to work.

Claire