Select to view content in your preferred language

Unable to change start and end time in Field Maps - Android

298
4
3 weeks ago
pslezak
New Contributor

I am unable to change the start/end times when creating a survey polygon in Field Maps (mobile app). For example, if I'm creating the polygon at 11 AM and want to enter the start time as 9 AM (2 hours earlier), when I choose 9 AM on the clock pop-up and click "OK", the time reverts back to 11 AM (current time). Even if I submit the polygon and try to go back and edit the time, I cannot choose a time earlier than the current time. The issue occurs for multiple maps I'm using.

I have tried reinstalling Field Maps (version 26.1.1). Other people with Androids have mentioned the same issue (I am using a Galaxy S23 FE). I need to be able to change this in the mobile app - it is not feasible for me to edit the times in the web app later on. 

0 Kudos
4 Replies
ChrisDunn1
Esri Contributor

Hi @pslezak ,

I believe you are running into a known bug that should be fixed in a future release. In the meantime, you can get around it by changing the date first, then the time, then changing the date again. It's a few extra steps, but after a few times it should be pretty smooth.

Basically when the date/time picker comes up, pick an earlier day on the calendar, then tap on the clock and set the time you want. Then hit OK to go back to the form, tap on the date field again, then tap on the correct day (just don't hit the clock again or select "today").

That should allow you to at least get the correct date and time into your form.

Chris

0 Kudos
MarcMuehleisen89
Emerging Contributor

I have reported this behaviour beginning of March and it got recognized as BUG-000183357 
It is currently being reviewed.
In the meantime we are going with separate Date and Time fields for questions where we manually want to adapt time.

0 Kudos
MarcMuehleisen89
Emerging Contributor

Got the message that this bug will be solved in app version 26.1.2

0 Kudos
ChrisDunn1
Esri Contributor

You are correct - the bug should be fixed in the 26.1.2 release of Field Maps that went live today.

@MarcMuehleisen89 and @pslezak please let us know if you are still experiencing the issue after updating the app.

0 Kudos