Why does the Add Records thing happen and how to stop it

Question

Whenever I use repeat count I get a lot of weird things that happen.  The biggest one is the add records thing.  If it knows it needs 4 more then just add why make me click?

I get it so much that I want to know what is going on here and how to stop it.  I had to start counting myself and adding a constraint but it would work a lot better if repeat count would behave.

In this case it is a nested repeat.

Thanks

Anonymous User · Answer

Hi Doug,

Yes, the new "hidden" appearance will be a better option, compared to making the field relevant, not relevant, then relevant again. Defaults will work as expected on hidden appearance question types, basically it is the same as a visible question, you just cant see it on the form. This is different to hidden/calculate questions, and different to not relevant questions.

As for the default bug, this is not really a bug. When a field changes from relevant, to not relevant, to relevant again, we do not expect the default to be there, as it only gets loaded once when the form first loads. The same applies with repeats and nested repeats, and this gets more complicated with relevant and repeat count on nested repeats, and load order if very important with defaults. It is better to use a calculate instead of a default in this case.

Regards,

Phil.

dougbrowning · Answer

Thanks Phil.  I am now writing out the set of fields 30 times (5 in the group so now 145 more fields than using a repeat) and then hiding when needed.  Slowing the form down but all I got for now.

It did create a new issue however.  The old bug where default values are not applied to fields that come out of a relevant.  Any update on this one?

I guess I could try the new hidden appearance instead.  Not sure if the default works on those yet.

thanks

Anonymous User · Answer

Hi Doug,

I have finally narrowed down the cause. It is related to using repeat count on a nested repeat that contains a question with a calculation that references another question in the parent repeat. It creates a timing issue with the loading of the values and repeats, which nulls out the additional nested repeat record rows after they are initially created, but before they get populated with the values.

We already have a known issue with repeat count on nested repeats and calculations referencing parent questions. This is another example of that same issue, which I think you have reported previously via GeoNet and I worked on it with you: https://community.esri.com/thread/241314-nested-repeat-with-repeatcount-shows-add-records-box-now

Unfortunately the only work around is to not reference a question outside the nested repeat, or not to use repeat count on a nested repeat. I have updated the internal backlog issue with these new findings and examples.

Regards,

Phil.