Select to view content in your preferred language

Bug Report - Datetime elements not saving when used in a repeat

374
1
03-14-2024 12:15 PM
DuncanC
Frequent Contributor

One of our field staff reported a bug yesterday that I have been able to reproduce really easily but haven't figured out exactly what is going on.  I've been unable to find an existing bug report for it but that may be due to not using the right search terms.  Does anybody know if ESRI is aware of this / have a link and ideally a workaround? 

When a datatime question is used in a repeat I'm getting some very buggy behaviour.

To recreate I used this super simple form:

begin repeattestingExample text question
dateTimedate_timeDate
texttextbox1Text
end repeat  

 

Create 3 items in the repeat, filling in as I go, set the time, put something in the text box.  I used:

Repeat 1/3: 1pm : One

Repeat 2/3: 2pm : Two

Repeat 3/3: 3pm : Three

I scroll back and look at them, they are correct as I move backwards through the repeat. But when I push forward from 1/3 it takes me to 2/3, and the text is correct, it shows two, but the time is now showing 3pm. I just set that to 2pm and haven't changed it.  That's not good. I go forward to 3/3, then back all the way to 1/3 and now it also is 3pm.  Not good. 

I haven't put much time into going further to document all the bugs I'm finding just playing with that very basic test form.  Yesterday I found that if I edited the datatime and then move to the next element in the repeat it didn't save that edit, I had to click into the text box after editing the time and then it did save the change.

The user reporting the issue is on iOS, I'm testing on Android, it's present on both.

0 Kudos
1 Reply
GraceSKim
Esri Contributor

Hi Duncan, 

I hope you are doing well! This behaviour seems very similar to a defect that was logged quite recently. It is currently under review, but I encourage you to create a support case with Esri, as your well documented and tested post can be very helpful to the production team! 🙂 You can mention the defect number, BUG-000165769, and the support team at Esri will take it from there. 

0 Kudos