Latest Contributions by BarbaraWebster1

Hi Michelle, The syntax you're using for the multiline photos looks correct. If you attach the most recent version of the xls form, I could look into it a little more and see what might be causing that error message. Thanks! -Barbara ... View more

Hi Michelle, Sorry for the delay in getting back to you, you can use the following syntax for multiline photos: vertical arrangement: ${#incident_photos} ${$file | size:300:0} ${/}   horizontal arrangement: ${#incident_photos}${$file | size:200:0}  ${/} This blog post discusses using multiline photos in reports. Also note that if you include a space or line break before the closing ${/} tag, that space or line break will show up between each photo in the exported report. Thanks, -Barbara ... View more

Hi Mike, It is possible to build two surveys on the same feature layer if you want to be able to use data from one survey in another survey. See the Use Survey123 with existing feature layers documentation, and this tutorial also covers an example where one survey is used for an initial assessment and a second survey is used to collect more detailed information.  One approach to this kind of workflow would be to configure the surveys so if certain conditions in the first survey are met, a survey will appear in the inbox of the second survey for the user to complete. You could also configure a note question or pop up in the first survey to instruct the user to navigate to and complete the second survey. -Barbara ... View more

Hi Chris,  I was able to use your SVG as an image map after I removed the image from the group that it was in and reexported to SVG with the image embedded (see attached). -Barbara ... View more

It's hard to say what what's causing the problem based on that error message. If you are willing to send your XLS form and report template, I could look into it and see if I can narrow down the problem.  ... View more

Does your report template still include ${#SC1} ${/} placeholders to start and end the repeat? Those placeholders would still be necessary in addition to the if statement. ... View more

In the screen cap of your XLS form, it looks like the repeat name is capitalized while the repeat name in the feature report is lowercase. Repeat names in feature reports are case sensitive so that might be what's causing the error.  -Barbara ... View more

Hi Michelle, Have you tried ${if (sc1 | getValue:"count")>=0} instead of ${if sc1}? See the Report Template Documentation for more information regarding this method. This is the recommended method for hiding an empty repeat. We will update the feature report documentation to reflect this. Thanks, -Barbara ... View more

Hi Oladapo and Casey, We have made a change on our end, and this issue should be resolved now. You may need to update or reinstall the Survey123 app for the change to take effect. Thanks, -Barbara ... View more

Hi Karl, You can access a collection of templates in Connect if you go to New Survey>Community. You will then be able to create a new survey based on that template.  Thanks, -Barbara ... View more

Hi David, Can you send your XLS form so we can look into this issue more? Thanks, -Barbara ... View more

Hi Erin, You could use an if statement in a calculation field to automatically populate the contents of the property address field if a 'property address is the same as mailing address' checkbox is selected. Here is an example of how that might look in the XLS form.  If 'yes' is selected, the property address will be populated based on the contents of the mail address field, of not then nothing is returned and the user will fill out the mailing address field.  There is further documentation on how the if and selected functions work at ArcGIS Survey123 Formulas. Thanks, -Barbara ... View more