I have two survey's that respond to one hosted feature service. One is a request that is submitted in the browser and the other is how inspectors respond to that request using the app. The now() on the DateTime field for the request works but it doesn't work on the inspection side in the Survey123 app. Please let me know if this is a bug or if I have something wrong with my code. Thanks!
Hello @FredMitchell,
I don't think this is so much an IOS 15 issue I can reproduce on my Android device and on an IOS 14 device. I had also tested with 3.12 and was able to reproduce with that version as well. I think the issue is more so around calculations not triggering when opened via the inbox. We have an enhancement (ENH-000134563) logged to enable calculations to always work on load from the inbox which I think would address this issue. One workaround would be to add a simple yes_no choice question at the beginning of the form and make the inspection information group relevant based on 'yes' being selected. Making the group relevant will trigger the calculation when the survey is opened from the inbox. I've attached a slightly modified Mosquito Control form for reference.
Hi- I am having a very similar issue .
I have two surveys linked to the same hosted feature. One is for the field staff to collect information and the other is for a committee to review the information from within a Dashboard.
I am using s123 Connect 3.13.239.
I have a dateTime field with the default field set to now() .
Should also note that I tried today() in the default field, as well as change the field type to date instead of dateTime.
In both the s123 Connect preview and when I launch the survey independently in browser, the Date of Review value is populated as expected.
But, when I put this survey into my Dashboard (where review staff will be able to see and jump around from issue to issue to review, the Date of Review field it is empty:
Testing out a few things, when I did add the now() to the calculate field it gets me a bit closer to auto filling the value, but I still have to hit the "reload" button to get the date to populate as expected.
Thank you thats exactly what I was looking for! I just encountered the bug where the now() function is not working in the calculation column when loading the survey from an inbox.
By chance, is the release of 3.14 still expected for the end of the month??
Thanks again
Hi @FredMitchell @ABishop,
Just letting you know we have recently updated the 3.14 beta builds on the Early Adopter Community and the next release will include major improvements to the expression calculation engine, new calculation modes, improvements to loading relevant questions and repeats, and other fixes to repeats, nested repeats and repeat count. With these improvements we see faster loading surveys, increased stability, less crashes and ability to optimize calculation workflows.
The issue you reported above can now be solved using the new calculation modes available in the latest 3.14 beta builds, where you can set calculations to always run or be manual or auto.
Please refer to this blog post for more details: https://community.esri.com/t5/arcgis-survey123-blog/arcgis-survey123-3-14-beta-now-available-for/ba-p/1124459
Direct link to EAC announcement: https://earlyadopter.esri.com/project/article/item.html?cap=e69ef91f45744b98882c651f7b518eb7&arttype...
Regards,
Phil.
@ZacharySutherby, just in case the enhancement you mentioned doesn't fix the issue I'm having I've logged a separate one under ENH-00143976. Thanks again for all your help!
Hi @ZacharySutherby,
Thank you for your thorough response to my question. I didn't realize that when a form is loaded from the inbox it's treated differently than if it's opened in the browser. I see what you did there with addition of the prior question making the group relevant depending on the response to that question. It's a neat idea but I think for now I'll keep the now() expression in the calculate column instead of the default one. Whether it's in calculate or default it works once the user taps on the DateTime field but I like that when it's in calculate it gives the refresh option icon to the right of the field. From a UI/UX standpoint it's a little more intuitive for our field workers since it's an actual icon for them to click. Also, one of the downsides of having the group be relevant is that if they select no on start survey they could possibly still go through and submit the survey but bypass the first group of questions which is a risk I'm hesitant to take.
In regards to the ENH-000134563 enhancement is there an estimated idea of which future release this would be included in? Thanks again for your time! I really appreciate it.
Respectfully,
Fred
That's an interesting observation. I tried the inspector form in the browser and the now() function worked. It is likely that this is a bug with capturing the device time from iOS 15. Inspectors are currently populating the field manually ever since now() stopped working.
@FredMitchell
When you test both of these forms are they from the same device and using the same connections, etc? Seems as if one is from a browser and the other is from an inspector response, could be the connection or device the problem?
Maybe try changing the inspector form to choose the time and date manually instead of autocalculating it.
I read the article but still am arriving at the same problem. The article states:
"Survey123 accepts three possible values in the XLSForm default column:
I have placed this expression in the default column of the unique DateTime fields for both surveys and it's oddly not auto populating for the second one.
Try reading up on the way the time works in Survey123 here:
https://community.esri.com/t5/arcgis-survey123-blog/dates-and-time-in-survey123/ba-p/895528
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
