Latest Contributions by JillianStanford

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 ... View more

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! ... View more

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!   ... View more

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 ... View more