Latest Contributions by AnninaRupe1

‎06-20-2025

Thanks. I understand, I think! Of course when I have a possible solution I don't need to switch anything out 😂 I'll try this when I can!

‎06-19-2025

Thanks for the suggestion. I will definitely look into this. Do you think that this solution would work on pages that don't have web maps? For this I'm just using a table. It's so users can filter data for reporting purposes.

‎06-17-2025

Unfortunately, I can't overwrite. The layer that ExB is referencing is a joined view feature layer. The original base layer was created for and is still attached to a Survey123 form and whenever I have to update the form (adding to domains is the most frequent task), I have to delete the joined view feature layer (even remove it from the recycle bin!) before the form can be republished. If I try to republish the form without deleting anything, it won't--it just spins.

‎06-16-2025

Yes! Or, if data source C has the same attributes, be able to apply the same configurations.

‎06-13-2025

Thanks for the reply, @Allen_Zhang. Unfortunately, no. This filters the entire layer for the entire Experience. I need to have different filters and views on different pages. When I have to delete the feature layer view from ArcOnline, recreate it, and link it back to the Experience pages, I have to build the filters/views all over again. I would like the filters/views that I built to not be tied directly to a feature layer, or at least be able to copy/paste to another.

‎06-12-2025

Does anyone know if a view can be made available Experience-wide? A little more information: I have an Experience that references several sets of data. These datasets were created in the same formats, mainly so they could be easily understood and didn't require definitions for each attribute in each dataset. One of these attributes is called "Site State." On several pages, I filter the tables and create views for filter widgets based on the region that page is referencing, which focuses on a subset of states. For each page, I have to create a filter on the table and then create a new view for each region. This wouldn't be as big of a deal but the data being referenced are from a view layer, which, if I have to update anything (e.g. domain choices), I have to delete the view layer, update the original layer, recreate the view layer, fix the broken data references in ExB, and then recreate all the filters and views. It would be nice to be able to filter or create a view once and then reference it throughout the Experience and not have it linked to a specific dataset.

‎05-29-2025

I am having a similar issue--the pulldata function is intermittently not working. Anyone have any ideas what might have changed in the past couple of days? This is preventing users from being able to submit a survey. UPDATE: the record that was being pulled had an apostrophe in the text. Once I removed that, it worked. Any chance this could be fixed? @DougBrowning

‎04-09-2025

Thanks for the suggestions. I spent a couple of hours this morning testing and neither options work. 😢 I feel like the first should work, and I got the URL to include the time = now() parameter without error, but the question still sees survey 2 in the state it was in when survey 1 loaded. The second doesn't work because there's no calculation. However, I did try adding a "recalculate" parameter to the URL, but that failed, too. Appreciate the ideas...and any more anyone can provide. I feel like this is a common task and am curious how other organizations do this.

‎04-08-2025

I have a survey where a user can collect data regarding a site (survey 1). In addition to geometry (polygon), the survey consists of select one, select multiple, dates, repeat questions, text, and attachments. One section in this survey is landowner contact information. To reduce data input and for quality control (since a landowner can own more than one site), I have a separate survey where the user enters landowner contact information (survey 2). This includes name, address, and phone number. This is basically a digital address book. I have connected survey 2 to survey 1 by using "search" in the appearance field in Survey123 Connect in survey 1, which points to survey 2. The user can start entering a landowner's name and select it from the list. Then in subsequent questions, the data auto-displays. However, this workflow only works if the landowner data has already been collected. If my users start survey 1, start typing a name and it's not in the list, they have to discard the survey, open up survey 2, complete that, and then go back to survey 1. I have tried embedding a link to the second survey in survey 1, but since survey 1 has already been started, and even if survey 2 is completed in a new tab, survey 1 doesn't "see" the new record. The user still has to refresh survey 1. Any ideas on how to get survey 1 to "see" the new record? Or, even better, if the contact doesn't exist in the list when queried in survey 1, give the option to create a new contact there?

‎03-31-2025

That totally makes sense now! Appreciate the explanation. I did a quick search but couldn't find anything: do you do blog posts regularly? I'd be interested in reading those, if you can provide the location. Your explanations are so well constructed; I can understand the logic much better than any other Python source I've come across.

‎03-28-2025

@RichardFairhurst : Thank you for such a great resource. I've been able to implement a solution using "Example 3 - Transfer of Multiple Field Values between Feature Classes involving Complex Field Manipulations" and am trying to understand a part of it: In line 23, updateRow[1] refers to the URL field ("UrlField1") of the update feature class and valueDict[keyValue][0] is the value field ("ValueField") of the source feature class. I'm wondering why the valueDict[keyValue] is [0] and not [1]? In the sourceFieldsList, "ValueField" is in the second position and since Python starts from 0, shouldn't that value be [1]? The "UrlField1" is in the second position in the updateFieldsList, so I expect it to be [1]. Obviously your code works, I'm just trying to learn! I'm sharing this with my colleagues because it's been so helpful!

‎03-26-2025

Talked with Esri Tech Support and found that the issue is fixed if the appearance setting that I entered (minimal) is removed so the cell is empty. Not a huge deal for me to keep the question expanded. Just thought if anyone else was having this issue that I'd let people know of the solution!

‎03-04-2025

If I'm understanding correctly, I would try something like this in the calculation field: if(selected(${accessible},'No'),"N/A","Inlet and Outlet") If the accessible question is marked "No," return "N/A," else return "Inlet and Outlet."

‎03-04-2025

This worked for me: https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-download-survey-data/ba-p/1141835

‎03-03-2025

Thanks for your response. I've tried this but it doesn't work. 😞 @ZacharySutherby @JenniferAcunto

Online Status	Offline
Date Last Visited	‎07-01-2026 12:36 PM

My Ideas

Latest Contributions by AnninaRupe1

Re: Experience-wide Views

Re: Experience-wide Views

Re: Experience-wide Views

Re: Experience-wide Views

Re: Experience-wide Views

Experience-wide Views

Re: [URGENT] Inconsistent Data Retrieval in Survey123 Using pulldata()

Re: Submit a second survey if data doesn't exist in the first survey

Submit a second survey if data doesn't exist in the first survey

Re: Turbo Charging Data Manipulation with Python Cursors and Dictionaries

Re: Turbo Charging Data Manipulation with Python Cursors and Dictionaries

Re: Conditionally required question works in Survey123 Connect desktop testing but not in published survey

Re: Survey123 Report Syntax Select Multiple Help

Re: FC Attachment Downloads and save

Re: Conditionally required question works in Survey123 Connect desktop testing but not in published survey

Re: Field Maps App Immediately Crashes

Re: Field Maps App Immediately Crashes

Re: Field Maps App Immediately Crashes

Re: Field Maps App Immediately Crashes

Re: Map Properties: Clip to an outline: Layer Clip...