Survey results differ when using phone app vs. web browser (or Survey widget in Experience Builder)

[ZackHutcheson]

I created a survey in Survey123 Connect, published it to our organization's account, shared it to a group, and deployed the survey via a widget in Experience Builder. Several of the questions in the survey form pull data from a URL (using the calculation field), thereby pre-populating several questions (i.e. council district, lot, block, ZIP, zoning, etc.) based on the location of the selected point.

When the survey is completed using my phone's Survey123 app, those fields are correctly populated in the survey form on the phone and in the resulting feature service's table (see highlights in image 1).

I also created an Experience Builder application using the Survey widget. Same process. When the user fills out the survey and selects the geopoint on the map (referencing the same web map as on the phone), none of those fields are pre-populated, and once the survey is submitted via Experience Builder, the records are NULL, when they should have a value (see image 2).

Any help or insight would be appreciated.

[ZackHutcheson · Accepted solution]

The issue stemmed from the syntax contained in the pulldata calculation in Survey123 Connect. There was a leading space from the third input parameter. Removing this space resolves the issue.