Latest Contributions by Jim-Moore

Hi Alex Glad to be of assistance! Thanks for the additional info. Could you please confirm your field app version number? The latest release build is 3.3.64. Also which device(s) are you using? Best regards, Jim ... View more

Hi Jodie Thanks for the details. Would it be possible to provide your XLSForm and .js file so I can investigate? Also could you please confirm on which version of the field app your users are seeing the issue? Thanks & regards, Jim ... View more

Hi Alex Thanks for the XLSForm. The very large external choice list in your survey (50,000+ rows) is likely the main thing affecting performance. One option is to try the 64-bit Beta versions of the field app and Connect. These are available for download on our EAC: https://earlyadopter.esri.com/project/article/item.html?cap=e69ef91f45744b98882c651f7b518eb7&arttypeid={4d0c881a-e4c4-4530-846f-512df374efc3}&artid={822F21C0-1BC6-4B9B-80FC-A43C1E9823C5} I did not encounter any issues in the web form. What specific issues are you seeing? Which browser are you using? A couple of other things to try regarding performance: Remove extraneous fields from the external choices tab (i.e. image and language columns). A choice list can be used by more than one question, so you could have one yes/no list on the choices sheet to use with all select_one questions (see attached example). Please note 'condition' is a reserved keyword (see types tab for a full list). These keywords should be avoided for question names. A couple of ideas where question relevance is concerned: The or statements you've used in your XLSForm are logical; however in the relevant column there are four unique scenarios (categories?). So one approach would be to determine which category the selected condition is in, and then set the relevance of each question based on that category. One benefit of this approach is that if you need to modify a category, it only needs to be changed in one place. Please see attached example (you might choose to make these category questions hidden). Another option would be to put the category into the name of the condition, for example you could prefix each condition with c1, c2, etc. and then in the relevant column use something like contains(${condition},'c1') etc. Best regards, Jim ... View more

Hi Alex If possible, could you please share your XLSForm so I can investigate? Thanks, Jim ... View more

Hi Francesca, glad to hear you got it working. Please let us know if you have any further queries. Regards, Jim ... View more

Hi Rosemary Thanks for the error messages and details. This looks like it's being caused by a known issue where a report template will not generate if a field name inside a repeat contains the repeat name (in this case the string 'FrontDamage' is the name of the repeat and also in the names of the text question inside it). We are working on a hotfix for the website which should be released soon. I'll post any updates to this thread. Please see more discussion on this here (including a workaround). Thanks & regards, Jim ... View more

Hi Kaitlyn Your calculation for the majority of the signs is good, however you could drop the brackets around height, e.g. (${width} * ${height}) div 144. You should be able to specify a different equation for each sign type with a nested if statement in the calculation column. Please see this handy information on using formulas in calculations, which lists the functions and operators you can use (including if statements): Formulas—Survey123 for ArcGIS | ArcGIS  For example: (SQUARE(Height/12)) * .76 would be something like: pow((${height} div 12), 2) * 0.76 ((1 + (SQRT(2))) * 2) * (SQUARE((Width / 12)/2.4)) would look something like: ((1 + sqrt(2)) * 2) * (pow((${width} div 12), 2) div 2.4) Hope this helps. Best regards, Jim ... View more

Hi Jennifer, confirming we've logged the issue with the ${field1 | selected:"1"} feature report parameter, and this will hopefully be addressed in an upcoming release. I'll keep this thread posted with any updates. Thanks & regards, Jim ... View more

Hi Jennifer Thanks for the XLSForm. Confirming the integer field type is causing the issue. If I clear the bind::esri:fieldType column and re-publish, the ADMIN_FIN40 field defaults to string field type and the check-boxes in the report work as expected. I will check with my colleague for some further information about the template syntax. In the meantime, if you need this value to be stored as an integer one workaround would be to add a hidden field with integer field type and use the int() function in the calculation to convert the ADMIN_FIN40 response to an integer, e.g. int(${ADMIN_FIN40}). Best regards, Jim ... View more

Hi Yorlady Currently, choice filters (cascading selects) do not work with select_multiple questions and it is not possible to use a function to dynamically update the choices for a select_multiple. A feature enhancement request already exists for this issue; I've added your comments to it and will update this thread if/when more information is available. Best regards, Jim ... View more

Hi Jennifer Thanks for the error messages and details. This looks like it's being caused by a known issue where a report template will not generate if a field name inside a repeat contains the repeat name. In this case the string 'RMMAL27_Y' is in the name of the repeat and also in the names of the questions inside it. We are working on a hotfix for the website which should be released soon. Please see more discussion on this here (including a workaround). For your second query, it looks like the integer field type could be causing the error. If possible, could you please share the XLSForm and report template for your survey so I can investigate? Thanks & regards, Jim ... View more

Hi Ian Unfortunately, select_multiple questions do not support calculations. I've added this as an enhancement request and will update this GeoNet discussion if/when it is addressed. As an aside, while perhaps not suitable in this case, it is possible to specify a default for a select_multiple question as described here: Prepopulate answers—Survey123 for ArcGIS | ArcGIS Kind regards, Jim ... View more

Hi Dion This is a known limitation when generating reports from an ArcGIS Enterprise feature service. When a survey response is submitted to ArcGIS Online via the Survey123 field app or web form, each image attachment is given a keyword based on its question name (i.e. as a way to associate an attachment with a particular question). The feature report template uses this keyword to reference each image. However, keywords are not yet supported in ArcGIS Server, so a feature report will not be able to retrieve images from a feature service hosted on Server. The team is working on supporting this capability for a future release of Enterprise. I will update this thread when more info is available. For more discussion on this issue please see: Survey123 Generate Report Error when Attachments Included  https://community.esri.com/groups/survey123/blog/2017/07/26/introducing-custom-form-report-templates-in-survey123-for-arcgis  Known issues—Survey123 for ArcGIS | ArcGIS  Kind regards, Jim ... View more

Hi Rawand, thanks for the XLSForm. I've tested your survey on the latest version 3.3 (which was released today) and I'm not seeing this issue. If possible, could you please try it out with version 3.3 and let me know if the issue persists? Thanks, Jim ... View more

Hi Rawand, you can attach files in the advanced editor (click "Use advanced editor" option in top-right of the reply panel). ... View more