Latest Contributions by ZhifangWang

Hi @GregReinecke , The open/closed setting is saved in the form.json file (settings.openStatusInfo) for a survey published from the Survey123 website or the <surveyName>.info file for a survey published from Survey123 Connect. Technically, you can use a script to update this setting in the file and then update the .zip file at the /data endpoint of the form item. If your survey was published in Survey123 Connect, another workaround might be utilizing the `format-date(${date1}, '%a')` function to get the day of today. Then set corresponding questions to be always invalid and required or hidden to achieve the goal.   ... View more

@KyleWeaver @EricAndersonMIT @A_MN , The 500 error and the issue "started (early) in November" both indicate that this is probably caused by the backend feature layer. The Survey123 website just got updated on 11/14 (PST) (so does Survey123 Connect/field app later) but no change during the end of October or early November. To confirm this: Is that possible to confirm the time of the first failure is after 10/25? Which was the date of ArcGIS Online's latest update. Trying to add a new feature to the backend feature layer used by the survey with large attachments in Map Viewer to see if the issue exists. (Survey123 uses a different approach to submit features/attachments than Map Viewer, this result may not be useful if Map Viewer works as expected.) If either case confirmed, as James mentioned, it would be best to work further with Esri Support or your distributor on this issue.   ... View more

Hi @A_MN , Thanks for sharing the XLSForm file. I've published it (with a minor modification to remove the input mask of the first question) from 3.18 version of Survey123 Connect, with setting of Options->Images->Unrestricted to allow image larger than 1280px. Then tested with filling all image questions with a 4000px*3000px image (23 images in total), but I can upload and submit the survey successfully in both 3.18 field app and 3.18 web app. Are there any specific steps I missed to reproduce the issue? Or if possible, can you please share a screen recording that shows how to reproduce the error? ... View more

Hi @A_MN , Does this issue occur in the Survey123 web app or the field app? If the survey was published in Survey123 Connect, would you mind sharing a minimal part that can reproduce the issue? In addition, you mentioned it might relate to the image size, regardless of the photo quality, is that passible to submit the survey if the image size (long edge?) is smaller than 1980px? ... View more

Hi @MelP , The knowledge base article you referenced is the correct one to generally solve this error. Can you please confirm that "Creator Data Editors" see the red error message for all survey records (including ones submitted by themselves) or only records that submitted by other users? If all records raise the same error, it means the feature layer (view) behind the survey is not shared appropriately. If only records submitted by others raise this error, it means detailed settings in the behind feature layer (view) is not correct. In addition, can you please confirm if your survey was published from Survey123 Connect or the Survey123 website? ... View more

Hi @JasminePrater , Thanks for sharing the screenshot. So the workflow in your app is: 1. In a Map widget shows the asset layer, the end user clicks on an asset. 2. A new inspection (geometry) is added on the map, and the Survey widget shows up to collect inspection  data (attributes). You would like the new inspection geometry point to snap exactly to the same location of the asset. Can you please confirm if this is correct?   ... View more

Hi @JasminePrater , Would you mind sharing a screenshot of the issue "the survey point isn't snapping to the asset."? Just want to ensure I understand this issue correctly. ... View more

Hi @JeetzPatel , > I upgraded the Mobile Worker to a Creator | Publisher, and he still has the same problem. If this "mobile worker" now has the same privileges as the "another user (Publisher)" and uses the same report template and survey data, it sounds a little strange that one can print the report while one cannot. Can you please help check the following to help us understand more details? 1. Try to remove the map statement from the report template to see if the mobile worker can print the report successfully? 2. If it's related to the map, check if the mobile worker can access all layers/data in the web map. 3. Any other differences between the mobile worker and the "another user (Publisher)" after you "upgraded the Mobile Worker to a Creator | Publisher" ? ... View more

Hi @Caitlin_Todd_LCOR , The fix to this issue (BUG-000157091) is available on the Survey123 website now. To make it work, just ensure your survey is published in at least the 3.18 version of Survey123 Connect or later than June 2023 on the web designer. Thanks again for your feedback. ... View more

Hi @ErikHerbergMETC , The fix to BUG-000157091 is available on the Survey123 website now. To make it work, just ensure your survey is published in at least the 3.18 version of Survey123 Connect or later than June 2023 on the web designer.   Thanks again for your feedback. ... View more

Hi @BrianRigwald , There is an additional "press-to-locate" value set in the appearance column for the geopoint question, this means "ask the device location when user answers this question". Leave the appearance column empty and set the default column as "null" will work: the device location is only asked when user clicks the locate button. ... View more

Hi @LeahClark , The issue you mentioned can be referred "BUG-000155815 Empty pages appear when a group with a field-list appearance has a body::esri:visible expression that equates to false when using the ArcGIS Survey123 web app.", and it has been fixed since the 3.17 version of the web app. Can you please confirm your survey was published in a version of Survery123 Connect >=3.17 version? If not, you can test the fix by appending "?version=latest" to your survey. Once satisfied, republish your survey using the latest 3.18 version of Survey123 Connect.   Thanks, Zhifang ... View more

Hi @JohnWatson_EBA , The fix to the preview issue of a report is available via the Survey123 June 2023 Update. Thanks again for your feedback!   ... View more