nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Overwriting time question when cycling through repeats

GeorgeClutterbuck

Using survey123 connect I have created form containing repeats which contain a time field. If I cycle through the repeats once filled out, the time field for all the repeats change to the most recent entry. I've tried using the once( function and changing the bind parameters to manual calculation and this works fine before publishing the survey on desktop, but the error perists on the field app and post submission. Any thoughts?

Thanks.

Najděte více příspěvků označených jako

Accepted answers

RobertAnderson3

You did indeed, it mentions BUG-000165769 - dateTime values overwritten when navigating through repeats.

What's new in ArcGIS Survey123 (June 2024) - Esri Community

As of release 3.20 Survey123 on June 24, 2024 this issue should be resolved.

All comments

PanGIS

I am struggling on the same, finger crossed I managed.

I would say that depends on the type of calculation, one solution does not fit all.

Have you tried to use "calculationMode=whenEmpty"

GeorgeClutterbuck

yeah tried that, looked fine on the desktop but then wrong on the field app, frustrating.

dougbrowning

Wrap it in once() works well for me

abureaux

I literally just had this come up after no issues. Will be trying once() myself (as @DougBrowning suggested).

GeorgeClutterbuck

did you just do once(now()) for the calculation and it was fine? or did you set the parameters field to manual also? I saw your previous response to a similar post.

dougbrowning

I have been using just once(now()) for years before the calculation modes were added. So far been ok.

RobertAnderson3

once() is definitely a good solution, I've been liking calculationMode=whenEmpty for calculations as well.

If you're just looking for it to capture now(), could you put it in the default column instead of the calculation column?

MatthewDesjardins

I am experiencing something similar, but I'm not sure if it's the same. For me, the issue occurs even if I'm not trying to use a default value, so a once(now()) doesn't seem to be relevant. Even if I do use that, or use calculationMode=whenEmpty, the same thing happens when the user manually enters a value.

In particular, the issue is that when you manually enter a time on the second repeat entry, if you page back to the first one it looks correct at first, but its value has actually changed if you try to submit it now; once you go back to the second and then return to the first again, it shows the same value as the second entry.

For me, it seems to happen with both time and dateTime questions, but not date questions.

However, the survey seems to work as expected when using the web app, as well as using a mobile application (I've only tested it on an iPad). But using the Windows Survey123 application, it behaves the exact same as Survey123 Connect does, with the time question being updated with the later repeat values.

Survey123 Connect is version 3.19.116, and Survey123 is version 3.19.121.

Edit: I tried it with a very simple form just containing these lines and no calculations. I also tried setting calculationMode to either manual or whenEmpty, despite there being no calculation being done, but it behaves the same.

type	name	label
begin repeat	TestRepeat	Test Repeat
time	TestTime	Test Time
end repeat

KaijaKlauder

Having the same issue as described nicely by MatthewDesjardins, in both Survey123Connect and as implemented on mobile devices. Connect is version 3.19.116, and Survey123 is 3.19.121. The field is a time field but I confirmed that changing it to dateTime shows the same behavior.

I have tried calculationMode=whenEmpty and also calculationMode=Manual, in each or all of the bind::esri:parameters, parameters, and/or calculation fields, which did not change the behavior.

Using once(now()) in the calculation field (with or without parameter specifications) results in sequential time stamp values that stay put if the user scrolls between repeats, but if the user manually edits any time value, the manually-assigned value is copied to all repeats. It's a slight improvement, but unfortunately because the time field of the first repeat calling once(now()) autopopulates when the form is opened (even if it's on a later page), if I don't start using those repeats right away, the values are no longer fresh and would need to be manually edited to be accurate. I'm collecting time series of animal behavior data and concurrent environmental stimuli, so having correct initial times and subsequent times are central to the data collection. This workaround would also run into issues when trying to collect an "end time" field that by definition will need to be blank for a while.

Any other suggestions to try before I kludge in a text field and make users manually enter times?

dougbrowning

Is there any kind of if statement connected to this date field at all? Anywhere in the chain

abureaux

My suggestion: Try again.

3.20 was rolled out this week (I just got it today). I am super certain that I saw a bug report for "date and time values in repeats being reset" marked as fixed for this release, but I can't find the post to confirm...

RobertAnderson3

You did indeed, it mentions BUG-000165769 - dateTime values overwritten when navigating through repeats.

What's new in ArcGIS Survey123 (June 2024) - Esri Community

As of release 3.20 Survey123 on June 24, 2024 this issue should be resolved.

abureaux

That's the one!

MatthewDesjardins

Thanks, that does seem to have resolved the issues that I was seeing!

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.