Title of the thread says it all. I have Inbox set up and repeats configured to allowUpdates and query. The existing repeats sync into the Inbox just fine, as long as I don't set a repeat_count parameter. If I set the repeat_count to anything, the existing repeats no longer download.
Is this a feature or a bug? Any workarounds?
Hello @PaulPetersen1,
A small test on my end isn't able to reproduce the same issue (same XLSForm attached). If possible would you be able to pass along your XLSForm for testing on our end?
Hi @ZacharySutherby ,
I did some more testing and figured out that it was because I had a relevant expression set on the repeat, and the form was opening with the relevant expression not satisfied...this was causing all of the attributes in the the first item in the repeat to be nullified. So the record was indeed being downloaded, but I would lose all of the attributes.
I thought I could perhaps use body::esri:visible instead of relevant, but since I have required questions in the repeat, it wouldn't let me submit the form.
Is there a way for me to get relevant-style functionality (ie, bypass required questions) without nullifying records?
Hello @PaulPetersen1,
The body::esri:visible expression is going the be the only option to conditionally show/hide questions/repeats without nullifying data. If the body::esri:visible expression is false the required validation won't check. You can also set up expressions in the required column to only make the questions required when you want them to be. For example you could make them required only if the survey is in "new" mode and not in edit mode, or only required if a certain question has been answered.
Hi @ZacharySutherby ,
Thanks for the tips. The problem is that even though body::esri:visible was false, the validations were still checking (although I received no messaging...the form just wouldn't submit).
I think I'm good to go know, though. What end up working was putting a conditional statement on my repeat_count so that the form wouldn't try to force-create a new record when not visible. And then I did set up conditional expressions on my required columns within the repeat as well. Now everything is working well.