nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Survey 123 Webform not auto-populating geolocation from CSV.

RVG296

I am trying to pull data from a CSV which has the lat long values for 4-5 cities and make the map automatically update when we select the cities. This is totally working fine in Survey123 Field and Connect, but the web version is not working. I used the right syntax for pulling lat lons in two different calculate types. I also made sure the data sources are correct. But still, I am confused why this error happens only in the webforms. When I look into the chrome developer console, I get this.

Attached is the xlsx file and CSV file.

CSVAirportLoc.csv.zip

Aviation Retardant Survey.xlsx

Find more posts tagged with

Accepted answers

All comments

RVG296

James Tedrick‌

Thank you James.

Once I removed the property('username') in the calculation, the survey worked fine on the Web too.

Not sure if that is the main issue behind this.

RVG296

Should I be changing that to String for {location}

JamesTedrick

Hi Rohit,

You can still have the bind::Esri:fieldType column remain null- I was referring to the bind::type column (these are separate, if somewhat closely named, properties).

RVG296

But I do not want {location} to appear in the survey. Thats the reason I have to use null. I also used the same process as per this esri tech support doc for setting up the location.

Error: Initialing Form... Failed to load data from (data source)

I think this was happening because I am using a calculated field to get the username (property('username'))in field type hidden But if I changed that type to Username and did the same thing, the webform worked fine. Not sure if that was the issue.

JamesTedrick

Hi Rohit,

It appears there is an issue in value conversion of your 'location' question. Forcing it to be a string by setting the bind::type field appears to address the issue.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.