Latest Contributions by JoseBarrios1

Hello Pan, Just for your information—I have a very similar workflow (a survey embedded in Experience Builder with several repeats-Web-Form), and I'm not experiencing the issue you're describing. In my case, I have a select_multiple question that's populated using a dynamic list via search appearance, and none of my questions are set to required. Even when I submit the repeat without filling out the first entry, the subsequent entries are still captured correctly. Hope this helps as a comparison! JB ... View more

Hi Neal, Thank you so much for your help with this. It’s been challenging because the query, (using ?), doesn’t even work in Connect, although it works fine on the web. It’s difficult to tell if the query isn’t functioning properly until the survey is published. Since my survey is primarily intended for web use, I’ll go ahead and implement the workflow you suggested as a solution. Thanks again for your time and support! JB ... View more

Hello Neal, Your approach works great on Connect, the mobile app, and the desktop app. However, it fails to load the list on the web app (see attached image). Unfortunately, the app is primarily intended for use on the web. Strangely enough, my current workflow behaves the exact opposite: it loads the full list on Connect, mobile, and desktop, but works as expected on the web app. Thanks everyone for the helpful suggestions so far — I appreciate the support in resolving this issue!   ... View more

Hello Neal, Thank you so much for taking the time to look further into this. I'm currently trying to implement your suggestion, but I'm having some difficulty adapting your code to fit my URL query. Would you mind taking a look at what I have so far? Specifically, I need to use orderByFields=ParticipantID so that the "Add Participant" option appears last in the list. I’m also using matches instead of where, as I couldn’t get where to work correctly in my case. Here is the current search() appearance expression I’m using:   autocomplete search("RCWParticipantsTable?url=https://services.arcgis.com/...../arcgis/rest/services/..../FeatureServer/0&orderByFields=ParticipantsID",'matches','PropertyKey',${PropertyKey})   Any guidance you can provide would be greatly appreciated! Thanks, JB ... View more

Hello Everyone, Thank you all for your suggestions and support. Unfortunately, I still haven’t been able to find a solution to the issue. Let me try to explain the problem I’m encountering in more detail, particularly as it relates to how choice lists are rendered and filtered in Survey123. Let me try to explain the problem I’m encountering in more detail, particularly as it relates to how choice lists are rendered and filtered in Survey123. Survey123 Performance Issue:  Survey123 is loading full datasets into choice lists before applying any filters based on previous questions. This result in long loading times and significant performance degradation. Here are some example of the workflow: On  Page 01- Site selection {State} – user selects a U.S. state {ProjectType} – user selects a project type (Federal, State, Private) {ProjectName_ID} – should display only relevant projects based on the selected State and ProjectType Expected Behavior: The {ProjectName_ID} field should: Stay empty until both {State} and {ProjectType} are selected Display only the filtered list of project names (10–264 records depending on filters) Current Behavior: All 1,200 records from the ProjectName_ID feature layer load immediately, before of prior selections If the selected ProjectType isn’t available for the chosen State, the {ProjectName_ID} list shows all 1,200 records, rather than remaining blank Only after both fields are selected does the filter apply correctly   Another example on Page 2 - Participant Activity Section This page includes 7 questions using the search() appearance to capture different participant roles (Submitter, Researcher, Tagger, Observer, etc.) Each question pulls from a list of 2,000 participant-role records linked to a {PropertyID} selected on Page 1 A participant can have multiple roles.  Expected Behavior: Each {Participant_Name} field should remain empty until a {PropertyID} is selected. Display results in autocomplete mode based on previous selection   Current Behavior: Each of the 7 text fields loads the entire 2, 000-record list before any filtering is applied This means 7 × 2,000 = 14,000 entries are rendered upfront autocomplete and minimal appearances are ignored  in survey123 connect in this layout. The autocomplete work as expected  when publishing the form on  the field app and web app. Performance is severely impacted until filters kick in.   Current Workflow Setup Using autocomplete appearance Form is structured using: Pages layout, dynamic-grid field-list, Inside a repeat   What I’ve Tried Reviewed all relevant documentation and tried workarounds provided here. Tried tweaking MaxRecordCount, but it doesn’t solve the issue: The filtered list varies from 10 to 264 records, so setting a static cap isn't viable Haven’t yet implemented the suggested workaround to set MaxRecordCount to 1 until previous questions are answered – I'm unsure how to do this dynamically   Summary of the Core Problem Survey123 is rendering full lists before applying filters based on previous answers. This leads to unnecessary data being loaded, unfiltered lists being shown to users, and severe performance issues — especially when using search() appearance within repeats or dynamic-grid layouts ... View more

Hi Molly, Thank you for your suggestion and for looking into this. I'm familiar with the Select and Query widgets in Experience Builder, and while each offers part of the functionality we need, neither seems to fully support the workflow. I'm starting to think this might not be possible without using the Developer Edition. It's surprising that such a common workflow isn’t already available in any of the standard apps. Thanks again for your help—I really appreciate it! JB ... View more

Hi Cody, I did look at the old Web App builder widgets but other than the draw tool, I could not find a tool that allow me to conduct the workflow I need! Thanks for your suggestion! ... View more

hi SarahRijneke To enable or disable columns (fields) available and visible at startup in the ArcGIS Experience Builder Table widget, first click on the Table widget to open the configuration panel on the right. Ensure the correct data source (e.g., “EELS_2025-Symbology”) is selected under the Sheet configuration section. Under “Configure fields,” choose “Customize” from the dropdown. Then click “Select fields for initial display” to open a list of available fields. In this list (as shown in the image), use the checkboxes to select which fields should be available to users, and use the eye icon next to each field to control whether the field is visible at startup—an open eye icon means the field will be displayed when the table loads, while a crossed-out eye means it’s hidden initially but still accessible to users. For example, in the image, both “FID” and “Program” are selected and have visible eye icons, meaning they will both appear in the table at startup. Once selections are made, close the configuration and preview the app to ensure the correct fields are shown or hidden as intended.     ... View more

Hello ENGEOGIS1 Absolutely — this is possible! If your data column contains values like "A, B, C" and you want users to type "A" and return all rows that include "A" (such as "A, B", "A", or "A, B, C, D"), you can configure this using the Filter widget in AGOL Experience Builder. Take a look at the screenshot to see the exact setup. Here’s how to configure it: Add the Filter widget to your app. Select the field that contains the multi-value entries (e.g., "A, B, C"). Choose the "contains" operator. Under Input settings, select “User input” and check "Ask for values" to allow users to type in their own search terms. (Optional but helpful) Add a Hint to guide users on what kind of value they should enter (e.g., "Type a letter to search, like A"). This setup enables dynamic filtering based on user-entered values.     ... View more

Hi GusC You can capture the 2nd value (indexed-repeat(${fp_name}, ${fw_pump_test}, 2) on a hidden question and pull that on the report. ... View more