Latest Contributions by JillianStanford

Thanks for your reply. The screenshot above is from the standard template. When published, the functionality does not work in the web version of the form. So, I think I am out of luck on that front. To your second point, 100% of users will zoom in to county or town level to submit their points. So, I can set a default zoom level but not extent because I don't know what county or what town they will be zooming in to. It will be somewhere in the state of Illinois. There appears to be no way to control the extent of a geopoint question at runtime. Even if the user uses the search bar to zoom to their AOI, when they add an additional geopoint to the repeat, it will be zoomed to the extent set at design time. It all technically works, it's just frustrating user experience. Thanks again.

Thanks for your reply. This is a form for the general public and we are limited to using the browser based version of Survey123. It is not based on a template but designed to update an existing hosted feature layer, this is all working as expected. We have one question that captures a geopoint in a repeat. This all works correctly for capturing the points in a related layer but the repeat is cumbersome because each time the user adds a record to the repeat the map zooms back out to the default extent (the entire state of Illinois). I can't configure a more specific extent ahead of time because the user may add the cluster of points anywhere in the state. The point overlay style seemed promising. In Survey123 Connect, I can see all the points entered in each repeat record. However when published, this style is not applied to the web version of the form. Thanks, Jill

Hi, I want to use the point overlay style described here - Point overlays on maps - to make repeats of geopoints more user friendly. This works great in the Survey123 Connect app - as I add more points to my repeat, I can see the previously entered points. However it does not work in the Survey123 Web version of the form. Can someone confirm that this is a limitation of the web form? The help doc says that "Geopoint symbology." is not supported by the web app but I am using the default symbology. Point overlays is not in the list of unsupported functionality. If this functionality is not supported, has anyone figured out how to make a geopoint question in a repeat more user friendly? In particular, I'd like the extent of each geopoint map in the repeat to be consistent. When the survey opens, the map defaults to the entire of Illinois. Users will be entering a cluster of points. When the user zooms to their area of interest in the first repeat, I'd like subsequent repeats to default to that first extent. Has anyone figured out how to accomplish something like this? Thank you!

‎04-23-2026

Hi, I am using Survey123 Connect to author a survey that is being used to edit existing records. When I configure a select_one field that is populated using the search function, when published, the style of the drop down is autocomplete, no matter which style options I configure. As an example, I have two select_one fields. The first one is populated from the values in the choices tab. The second one is populated from a feature service. Both have their style set to 'minimal' Within the Survey123 Connect app they both look correct as simple drop-down boxes. When published, the first one is styled correctly as a simple drop-down. I can see all of the options when a value is selected. The second one is styled as an autocomplete text box. If the field is not populated, it's okay because the user can see the available options (although I do wish the styling was the same). If that field is already populated the options are filtered by the text. So it isn't clear that you have to clear out the box to see all the options. Even if I choose a completely different style, like "compact", it is styled correctly in the app, with multiple horizontal radio buttons but is autocomplete when published. I assume this is a bug but has anyone stumbled on a work around for this? This is going to cause confusion. I have updated Survey123 Connect to the latest version (3.25.27). This behavior is consistent across different browsers. Thanks! Jill

‎06-17-2025

Is it still in your recycle bin? Unless you delete it permanently, it will still show up for 14 days.

‎02-12-2025

Hi, I think it would just be a feature class - Parameter data types in a Python toolbox

‎01-29-2025

Hi All, I'm upgrading an ExB Dev app from 1.14 to 1.16. I can also recreate this issue in AGOL Experience Builder. I am glad that the attribute table can now interact with the map, it is so much easier to set up and maintain. I'm having trouble with some of the tables appearing empty. I've narrowed this down to layers that have popups configured that don't have the OOTB configuration of a field list. For example, we have a layer that formats the display of attributes using the Text card. In the app, the table is empty but the record count is correct. It's possible to view the data if you use the Show/Hide Columns button but it's quirky - You have to click the "Show Selection" tab and then unselect and reselect each column you want to view. If you close the table or resize the app you have to turn on all of the fields again. We also have a couple of layers that are configured to use the Title card but not show any fields. We get the same empty table behavior. I see why it makes sense for the table widget to honor the visibility of the fields set in the popup but what is the work around for when you want the popups to be customized and the table to be useable? Thanks!

‎01-15-2025

I cobbled something together that worked for my specific use case. I posted it here - https://community.esri.com/t5/arcgis-experience-builder-questions/custom-widget-output-datasource/m-p/1381931#M10865

‎11-18-2024

From your first post it looks like UNITID is a string? Have you tried wrapping your where clause value in quotes? concat("UNITID ='", ${UNIT},"'")

‎11-15-2024

Hi, If I'm understanding correctly, what works for me is to retrieve the location from a feature layer into a hidden field as JSON and then pull out the x and y from that. Does that work for you?

‎09-12-2024

Hi Sarah, Thanks for the reply. It looks like I am using Survey123 Connect version 3.19.104. If I get a chance I will try your solution. As a workaround, what I ended up doing is denormalizing the records into a hosted csv and searching that. It's not as dynamic as I would like and is one more piece of content to maintain but it allowed me to keep moving forward. Thanks again! Jill

‎08-27-2024

Sure, I could do that but why store a value across two fields when I can store it in one? There must be other circumstances where you would want to present a value in a user friendly way in the survey and then store it in a more efficient way. Thanks for your response!

‎08-27-2024

No, because I'm not storing the feet and inches, I just want to store a single value that combines feet and inches into inches.

‎08-26-2024

Hi I have a scenario where I allow the user to enter a dimension in feet (max_width_feet) and inches (max_width_inches). I then combine these into a single inches value (max_width) and store that in the feature layer. This is working fine. What I can't figure out is how to populate the feet and inches fields from the max_width field when the user edits a previously submitted survey. If I try and reference max_width in the calculation parameter of max_width_feet and max_width_inches I get the following error: It makes sense to me that a field can't reference a field that references the first field but what is the right way to do this? Is it something to do with calculation mode? Or am I not using default and calculation correctly? Thanks!

‎08-22-2024

Can someone confirm for me that when searching a hosted feature layer to populate a select_one field appending query request parameters to the REST endpoint does not work in the web app? This limitation is not listed in the documentation but I get pretty funky behaviour. For context, I have a drop down that I want to populate from a hosted feature layer. I need to filter the values based on a previous selection but I need to search multiple fields so I can't use the searchType, searchColumn and searchText parameters. My solution is to query for the relevant records using the where query parameter. So, my appearance column looks like this - w3 autocomplete search(concat("list_town?url=https://services2.arcgis.com/aIrBD8yn1TDTEXoz/ArcGIS/rest/services/Towns/FeatureServer/0/&where=CountyIntersect_1=",${county}," OR CountyIntersect_2=",${county}," OR CountyIntersect_3=",${county}," OR CountyIntersect_4=",${county})) This works great in the Survey123 Connect app. When I look at the request in Fiddler all looks correct and the expected values show up in the drop down. However, when I publish the survey and open it in the web app, I get the following error: It's failing to load because it appears that the where parameter for the request makes no sense. Am I out of luck with this solution or do I need to configure the field differently? Thanks! Jill

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by JillianStanford

Re: Repeat of Geopoints - Point overlays in Survey123 Web

Re: Repeat of Geopoints - Point overlays in Survey123 Web

Repeat of Geopoints - Point overlays in Survey123 Web

Select_One style defaulting to autocomplete in web app

Re: Deleted view layer will not go away

Re: Geoprocessing Service with output Feature Layer

Empty Experience Builder Tables

Re: ViewInTable Data Action

Re: Survey123 Connect Pull location data for a geopoint from a hosted feature layer

Re: Survey123 Connect Pull location data for a geopoint from a hosted feature layer

Re: Query parameters in search appearance expression

Re: Referencing a field in calculation parameter

Re: Referencing a field in calculation parameter

Referencing a field in calculation parameter

Query parameters in search appearance expression

Item Usage Operation

Number of decimal places for esriFieldTypeDouble f...

Query parameters in search appearance expression

Re: Hosted Feature View Layer Automatic Updates

Re: Geoprocessing Service with output Feature Laye...