topic Re: Pulldata constraint stops working in browser, but functions fine when viewing in survey 123 connect. in ArcGIS Survey123 Questions

Pulldata constraint stops working in browser, but functions fine when viewing in survey 123 connect.

JoshuaCampion — Tue, 07 Apr 2026 19:39:19 GMT

I'm currently creating a survey to give citizens the ability to reports issues that they see on our highways. I created a buffer around the highways that are our (County Gov) responsibility to maintain. I then set a constraint for the geopoint question to confine responses to that polygon. It works fine when viewing the survey in connect, then I opened it from ArcGIS online in a browser window, and now it won't allow points to be submitted even within the set polygon. I read that the pull data line doesn't transfer over from the app to a browser well. Thanks for any ideas!

Re: Pulldata constraint stops working in browser, but functions fine when viewing in survey 123 connect.

Neal_t_k — Wed, 08 Apr 2026 13:11:25 GMT

Can you share the relevant parts of your xlsx or or pulldata calc?

Re: Pulldata constraint stops working in browser, but functions fine when viewing in survey 123 connect.

JoshuaCampion — Fri, 10 Apr 2026 13:56:16 GMT

pulldata("@layer","getValueAt","attributes.boundary","https://services1.arcgis.com",${location}) = "valid"

Since posting this I've realized that the problem might be that I'm running an attribute check rather than a geometry check, but still not sure. I also shortened the link for the purpose of posting here it contains more than just services1.arcgis.com. Location is the name of the geopoint question.

Re: Pulldata constraint stops working in browser, but functions fine when viewing in survey 123 connect.

Neal_t_k — Fri, 10 Apr 2026 14:39:15 GMT

I would start by putting just pulldata("@layer","getValueAt","attributes.boundary","https://services1.arcgis.com",${location}) in a calculation to see what it is returning, and if it is returning correctly in the web app as well. Then if that is working correctly in the constraint field put . = "valid" assuming "valid" is what the calculation is returning.