Hello Geonet Users,
I think it is the using a field called calculation. I changed it to calculation22 and now it works. It is not on the reserved list but I would not use it.
Hope that is it
Thanks for taking a look, I should not have used "calculation" as as field name. I made the change as per your suggestion though if you add multiple people before adding the HHID/City on page two only the last person
repeat will be populated with the values. The other records in the repeat have a refresh button next to them.
Since they will be hidden fields they will not recalculate once created. As a work around, I ended up putting a relevant HHID and City field before the Person repeat which populates the hidden HHID and City fields. I was trying to avoid having to create extra fields but ended up doing so this time. Attached is a revised example. Thanks again for taking a look.
Oh I just saw now you are using repeat count. That is prob your issue. Using repeat count preloads all the repeats at the start. This can cause all kinds of issues with calcs. I have posted on this but I cannot find it.
In the end I had to remove all my repeat counts as they just do not work right. 3.13 is supposed to tackle a number of these. Instead I count and they tell then with a constraint if they add too many. Works much better.
Try removing repeat count and see. I am not sure why you would use a repeat for just 1 record really. Maybe just testing.
But yes it will not go back through all the repeats and populate them if you change it later. I would not show the repeats until they pick a city then nothing to worry about.
Normally I also only push the key into a repeat otherwise you are just double storing data. If you say want to change the city then you have to find and change all of the subtables instead of just changing it in 1 place. They can get mismatched easily. It would be like storing your address in each individual bill vs just changing it in your person record.
Well hope that helps.