Latest Contributions by JamesTedrick

‎09-19-2023

Hi Alana, Instead of using external_choices, you should have a dedicated CSV and retrieve teh value from that. I'll note that the external_choices sheet is written into a CSV file called itemsets.csv, not external_choices.

‎09-19-2023

We are aware of this issue and looking into it.

‎08-28-2023

Hi @AndreaPecharich , Could you also share the JS function? It may be easier to e-mail it (jtedrick AT esri.com)

‎08-23-2023

Hi @RutledgeNicholas , The automatic reload setting cannot be set via Survey123 Connect; that being said, you can set it via the Survey123 website - go into the editing tab for the Connect Survey; while you can't edit the form layout, you can specify the option for the Thank You Screen and automatic reload.

‎08-23-2023

To amplify on @abureaux 's advice: <div> tags are normally displayed as block content, which means that the content following is placed in a new line after the <div> by default. Conversely, <span> is an inline content tag, which means that it won't place a new line afterward. If you still wanted to use a div, having the display: inline style property will change the behavior to the same as <span>.

‎07-25-2023

An 'Update XLSForm template' tool is now available in Survey123 Connect. For more information, please refer to the 'Update template' section of the Survey123 documentation.

‎07-25-2023

Rangefinder workflows with TruPulse devices are now supported in the Survey123 field app.

‎07-25-2023

The Survey123 Connector in Power Automate now supports producing feature reports.

‎07-25-2023

With the June release, Survey123 now supports the location sharing functionality available in ArcGIS.

‎07-07-2023

Hi, the issue in your example is where you are retrieving the x & y values. In your example, the values are retrieved from the attributes of the geocode result; these are values stored in the geocode table/index and are not altered based on the request input. Instead, you should be retrieving the values from the location object, which is reprojected as part of the request made by Survey123. The attached file shows this difference.

‎06-20-2023

Hi @JudithLandry - Apologies for the delay, we just noticed this comment. I think I see the issue you are describing - to confirm, this is not when you are passing the entire repeat set into a function, but you are passing a field within the repeat into the function - undefined values are being stripped from the set of values?

‎04-25-2023

Hi @Kara_Shindle , The where clause should be applies at the repeat tag ${Services} , not an individual field - the where clause sub-selects features form the repeat.

‎04-24-2023

As mentioned in the Additional Syntax section of the report query documentation, you can use a where clause in the repeat tag to limit the repeat records that are printed in a repeat section. ${#Services | where="Categories='Cat1'"}

‎04-18-2023

Hi @slach , The default behavior of the form is to request the user's location; because the request for a user's location completes after the browser has loaded the form values specified in the URL, that is overriding the value you provided when the form was loaded. You can prevent the request for a location by providing a default value of null .

‎04-18-2023

Hi all, Given these reports of functionality impairment, we have reverted the update to the feature report system. We would appreciate your help in diagnosing this issue; if you have an case open with Esri Support, I have asked them to forward your information to us if you are willing. Otherwise, please reach out at jtedrick@esri.com.

Online Status	Offline
Date Last Visited	‎06-11-2024 04:50 PM

My Ideas

Latest Contributions by JamesTedrick

Re: XLS form pulldata() not returning value

Re: Error: Initializing form...

Re: javascript not working after S123 version 3.18 update

Re: Survey123 Connect - Reload After Submission

Re: Survey123 Required Asterick Posting Below Question Label

Re: "Upgrade/Migrate" Older Version of Survey123 Connect Excel Form to a Higher Version - Status changed to: Implemented

Re: Rangefinder Offset Data Collection in Survey123 - Status changed to: Implemented

Re: Add support for feature reports in MS Power Automate (AKA MS Flow) - Status changed to: Implemented

Re: Survey123 Tracklog of Fieldworker - Status changed to: Implemented

Re: Custom Geocoder to Geopoint - Different WKID

Re: Extending Survey123 smart forms with custom JS functions

Re: Accessing related records in a Feature Report

Re: Accessing related records in a Feature Report

Re: Geometry defaults to users location instead of passed lat and lon coordinates

Re: Report Template Issue: parentLayer name

Re: Survey123 and SubTypes

Re: Force Carriage Return (new line) in a feature ...

Re: Error when generating a Report. (An error occu...

Re: Print fail started overnight

Re: EXIF pulldata() into existing Attachment Table

Wildfire Response GIS