Latest Contributions by AnninaRupe1

‎07-09-2025

I did some more testing: I modified the Flow down to the bare minimum so I could first test the Trigger: When a record is updated in a feature layer (related table) Get data from feature layer (parent table) Initialize variable (Apply to each) Fetch updated, changes, or deletions from feature layer (For each 2) Condition True (For each 1) Send an email False The Trigger works: I updated an attribute in the related table and it sent an email. However, the data in the email aren't correct. In my hosted feature layer, I have two polygons. One has one related record and the other has two related records. I only updated one attribute in one related record of the related table of the polygon that has two related records. I received two emails, both with the same data from the updated related table record but the parent polygon data were for different polygons. So it sent an email for both polygons but assigned the same related record to both. To me, this means that the related table isn't connected to the parent layer somewhere. I tried to put a condition in (ParentRecord (attribute from related table) is equal to GlobalID (attribute from parent layer)), but when the Flow is triggered, it follows the "False" part of the flow.

‎07-07-2025

I actually don't know the exact reason why the terminate, response, and initialization actions were needed. I have a Flow that's currently being used to copy from a hosted feature layer to an Enterprise layer (same workflow except without the related tables). I was having trouble with this last year and was able to use some technical assistance hours to get Esri help in creating the Flow. The analyst added these actions. I opened the Flow and made sure the connections were good and saved it. At the top of the Flow, it stated that it was ready to go (see the attachment called Save_Successful.png). Then, when I returned to the Flow's management page, it gave me an error (see the Flow_Checker_Error.png attachment). I then clicked on the "Go to the trigger" link and the Run Details stated that there was an "Error creating webhook" (see attachment called "Error_Creating_Webhook.png). I did a bit of research and found that I didn't have the "Keep track of changes to the data" setting turned on. After I updated this setting in ArcOnline, the Flow triggered. However, the conditions were set incorrectly so the Flow didn't complete. I updated the conditions and the next time I updated the attribute to trigger the Flow, it failed (see the Flow_Fail.png screenshot). The "For Each" actions wouldn't stop spinning so I can't see what the error is there. I also don't know why there are so many "For Each" actions; they just keep getting added when I added other actions to my Flow. The target layer is a hosted feature layer; not a view.

‎07-07-2025

I have created a brand-new hosted feature layer to test out my workflow; the record that's supposed to trigger the webhook is only being used for this new Flow and isn't being edited/deleted by anything else.

‎07-03-2025

@AkshayHarshe: I'm actually talking with a couple of solution engineers who will be reaching out to you more about my workflow! But for now, I don't have any errors to pass on because the Flow isn't being triggered, even though I updated the attribute that's supposed to trigger it. I basically copied the original Flow that runs fine and added the related table aspect, and now it doesn't trigger at all.

‎06-23-2025

I have been working on a Tool for a couple of years now and have been slowly updating it based on user feedback and needs. This Tool uses Microsoft Power Automate to copy a lot of data to different layers so users aren't having to do it manually. The last part of the workflow takes a polygon and some associated attributes from an ArcOnline hosted feature layer and pastes it into a feature layer on our Enterprise system. I had assistance from Esri to get this running (we had hours through our organization's agreement for technical help). I have attached a screenshot of the Flow (Copy_to_Portal_PA.png). I am now testing a process to see if it's feasible as a solution to a problem, and it seems like it will work, but I don't have the specific Flow steps correct. I again want to copy a polygon record from a hosted feature layer to the layer on our Enterprise system, but the hosted feature layer now has a related table. The trigger to copy the record is updating an attribute in the related table, copying the parent polygon, some of the parent's attributes, and some of the child's attributes to the Enterprise layer. I used this great post to be able to "see" the related table in Power Automate, but my Flow isn't being triggered. Based on the previous assistance I received from Esri, there is an extra step/missing step/wrongly nested step that's causing this, but I can't find it. Can anyone help? I've attached two additional screenshots of my new Flow (PA_1.png and PA_2.png) to show what I created. Please let me know if you need more information. @NataliyaLys @SeanKMcGinnis

‎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.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by AnninaRupe1

Re: Copy Record to Enterprise Feature Layer when Related Table is Updated

Re: Copy Record to Enterprise Feature Layer when Related Table is Updated

Re: Copy Record to Enterprise Feature Layer when Related Table is Updated

Re: Copy Record to Enterprise Feature Layer when Related Table is Updated

Copy Record to Enterprise Feature Layer when Related Table is Updated

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: 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...