Hi Survey123 hive mind,
I have a survey form embedded in an Experience Builder application where the user starts typing an address into a geocoded text field called address. This then places a point on the map for the geopoint question (a separate field called address_point with type = geopoint)) to give the survey a geometry when creating the point associated with it on the feature service. This bit works flawlessly thanks to this calculation:
concat(number(pulldata("@json",${address},"location.y"))," ",number(pulldata("@json",${address},"location.x"))) |
My issue is that when the user types the first bit of their address, the locator comes back with suggestions. When you click on the correct suggestion, the geopoint map zooms to the location, but the suggestion doesn't autofill into the geocoded text field. The user must click the suggestion again to get the autofill to work.
My concern here is that the address field in the table will contain incomplete address info as it will not be clear to the user that they have to click twice to get the address to fill. Frustratingly the autofill does work in about 10% of test runs.
I've tested this outside of Experience Builder and the autofill works fine so it looks like an ExB issue. Has anyone seen this behaviour before?
Solved! Go to Solution.
This is posted a lot. pulldata does not like being inside any calculation at all. Move the pulldatas to their own field then wrap those fields in your calc.
This is posted a lot. pulldata does not like being inside any calculation at all. Move the pulldatas to their own field then wrap those fields in your calc.