Latest Contributions by Jim-Moore

Thanks Joe, great to hear the issue is resolved. Jim ... View more

Hi Chris There isn't a way to control edits (in the way you're describing) inside the form itself. We have an open enhancement to be able to set the Sent box to read-only, so sent surveys could be reviewed after submission but not edited. I'll add your comments to our issue notes and endeavour to keep this thread updated with any progress (no timeline for implementation at this stage). Please see more discussion on this here: https://community.esri.com/message/729307-re-disable-copy-the-sent-data-to-a-new-survey-option And also in the comments for this Idea: https://community.esri.com/ideas/13543-restrict-updates-to-sent-survey-records-in-survey123 Best regards, Jim ... View more

Hi Michelle Thanks for the details (and the update!) - good to hear you got it to print. Our team is currently investigating an issue with feature reports that use a basemap with multiple vector layers, and/or reports with multiple complex basemaps. Does the basemap you're using have a large number of layers in it? Does the issue persist if using a larger map scale (i.e. less than 145000)? Would it be possible to share the link to the basemap, XLSForm and report template DOCX? (Feel free to send by direct message if you prefer.) Thanks, Jim ... View more

Hi Joe Were you able to resolve this issue? If not, could you please confirm which version of the web app you're seeing the issue and on which internet browser? Are you able to submit a survey and trigger the webhook successfully on this network connection using the Survey123 field app? Are you able to successfully trigger a webhook with another survey? It might be useful to use a web debugging tool (e.g. Charles, Fiddler) to take a look at the web traffic on submit to see if this provides any clues. Thanks, Jim ... View more

Hi KYTC GIS Thanks for the description and screenshots. During the publishing process, a new domain is applied to each select question as it's created, sometimes resulting in duplicate domains. So what you're seeing is currently expected behaviour, however this issue has been logged as an enhancement request to consider in the future and I've added your notes to it. We'll endeavour to update this thread with any progress. As you've indicated, this issue could also be raised as an enhancement request via Esri Tech Support so that it gets logged in the Support system with an ENH number that you can track, and other use cases can then be attached to it. Best regards, Jim ... View more

Hi Nate Thanks for your query. The first method can be partially achieved with reverse geocoding, which is detailed here and in this blog. Depending on the coordinates, locator service used, etc. the details returned may not exactly match what was originally typed into the geosearch bar. The second method you describe isn't currently possible, however we already have this logged as an enhancement request to consider in the future; I've added your comments to it and will endeavour to keep this post updated with any progress. Best, Jim ... View more

Hi Marlene & Chris Good catch Christopher L. Rogers! Just as some additional info, you can reference the choice name (as opposed to the label) by using getValue, which would look like this: ${if (photo_type | getValue:"")=="overall"} Please note that in a future release we intend to update the syntax to make it simpler, so that the name is referenced in the conditional statement rather than the label; in which case the original ${if photo_type=="overall"} will then work. Note that the getValue syntax will also continue to work following this change. We'll endeavour to keep this thread posted with any progress. Jim ... View more

Hi Marlene Thanks for the details. Removing the parentheses from your conditional statement should help, something like this: ${#photoRepeat} ${if photo_type=="overall"} ${photo | size:466.9:350} ${/} ${/photoRepeat} Hope this helps, please let me know how it goes. Kind regards, Jim ... View more

Hi Ying Zhang Are you launching the survey in the field app or the web app? Thanks, Jim ... View more

Hi Anu The related table view should work with surveys published in older versions. Could you please provide some screenshots to illustrate what you're seeing? Thanks, Jim ... View more

Thanks Florence Great to hear it's working well! I'm not sure how esriFieldTypeString ended up as the column header in your XLSForm; the bind::esri:fieldType column has always been part of the advanced template so perhaps it got overwritten somehow. You're correct, the latest version of each template is always available from the New Survey dialog in Connect, and the date a template was last updated is displayed here too: The templates are provided as a guide/starting point and once downloaded they can be altered to suit your needs (for example, removing irrelevant columns, shading cells to help with design, etc.), so we don't include the template version/date in the XLSForm itself. Best regards, Jim ... View more

Hi Florence, you should be able to overcome this by adding null to the bind::esri:fieldType column for the note questions. This will omit these questions from the feature service. Please find more info here: https://doc.arcgis.com/en/survey123/desktop/create-surveys/esricustomcolumns.htm Hope this helps, Jim ... View more

Thanks Yuko, I will add these notes to the request. Best, Jim  ... View more

Hi Monica Zhang, following from our conversation last week at the UC, just an update that we've logged this one to take a closer look at. As we saw in our quick testing, it appears the decimal questions with a decimal-time() calculation are being rounded to three decimal places in the web app, causing issues with subsequent calculations. I'll endeavour to keep this thread updated with any progress. Hope you had a great UC! Best regards, Jim ... View more