Latest Contributions by AnninaRupe1

I agree, it does seem backwards, but I think it has to be done that way because the attributes that the Condition uses to run are from the child table. I tried creating another flow starting with listening to changes in the parent record (because I agree with your theory that a child record wouldn't be updated without the parent), but again, when I click on the run to see what happened, sometimes it shows as expected (look, though, at the ! still displayed next to the Condition result, even though it says "False"): And other times it doesn't (I included what I think should be happening in the steps in this image): But, like you've mentioned in the past, the New Designer can be weird, and the old view shows it correctly. So, I tried then making the change to the child record and the Flow didn't run. At all. Even the original Flow (that is looking at the same data) wasn't triggered. I'm fit to be tied since I have to make the changes manually if the Flow doesn't run or runs incorrectly, but there's not an easy way to identify the changes!

Thanks for the best practices suggestions! Implementing now. I think I have narrowed down part of the problem. I don't think this accounts for all of the errors, but I made one modification at a time to see what the Flow behavior would be, and this is what happens: The trigger is "When a record is updated in a feature layer," and this is looking at a related table. The next 2 actions look at the same related table: "Fetch updates, changes, or deletions from feature layer" and "Condition." If the Condition action is true, I "Get data from feature layer" which is the parent feature layer of the related table. I use Advanced parameters to query the parent feature layer by the GlobalID field, that matches the parentrec value from the related table where the change was made. I need to do this because I need to copy the geometry and a couple of attributes and some attributes from the related table to a record in an Enterprise feature layer. I say all this because the Flow is actually successful when the change is made in the related table. However, the Flow also runs when a change is made in the parent record and not the related table. This is when I see the errors in the Condition action. Is this weird behavior? I would think that if a change was made in the parent record it wouldn't trigger since I reference the related record feature layer as the input parameter. I also looked for the Error table but couldn't find one. The only thing I could see is the Code View for the Condition and it just listed everything that should happen, not the output code.

Thanks to both @abureaux and @RyanAglietti ! They must've pushed some changes! I logged in this morning and noticed for almost all of my Flows I could just click on the trigger or action and see the "Layers in" and "Feature layer" parameters...and could see all of my possible inputs. I just made sure to save each after I clicked on each trigger/action to make sure the changes stuck. I did have to re-create one of my Flows, though, that didn't automatically show the new parameters. A day ago this didn't work!

Alright @abureaux ... This issue is intermittent. There are still errors in my Condition, and I can't figure out why. Here is my Compose input: And my Condition: (the Outputs is: outputs('Compose') ) But I still get errors and the Flow says it's successful! Is there anything I can do? I have to go into each run, check if it actually was successful, and manually fix it if it didn't.

Thanks for the quick response. I guess I should've been more clear: that "raw" URL is the part that looks funky, because of the URL code that's been added (e.g. %) when it shouldn't be replaced. While I was messing around, I copied the service URL from ArcOnline and pasted that as a custom value. That seemed to work. Unfortunately, that still doesn't get at the root issue--I'm logged in, my credentials have been re-authenticated, and I still can't see any layers after "N." I tried adding the layer to "My Favorites" in ArcOnline, and that doesn't come up. I even tried creating a new Flow using the "When a record is updated in a feature layer" for Enterprise trigger, but I was coming up with the same issue. Note: I'm not expecting the same layers, since they are in different systems, but I can't see layer names past "N" in the Enterprise system, either.

I've been having trouble with my Flow working, and to help troubleshoot, I want to try reconnecting to my Feature Layer in the drop-down list. When I click on my Trigger ("When a record is updated in a feature layer"), the feature layer that is listed has weird formatting (see image). When I remove the layer to select it again from the list, the drop-down shows the layers I have access to listed in alphabetical order. Unfortunately, the layers listed end at those beginning with "N," and my layer starts with "P." Anyone have any ideas on how to fix this? I've made a new connection and that hasn't worked. @abureaux

What a great explanation--thank you. I go back and forth between the classic and new designers; some things are only visible in one or the other (or, more likely, I just haven't found the locations!). Thanks for the explanation on the JSON; I've seen the inputs and outputs but didn't know that was what you were referring to. For the flows that fail, I don't get any JSON telling me what record (and attributes) failed. Most of the time it's just referencing the layer ID and not much else. I logged in to get you some examples of JSON from the failed Condition, but the outputs are different than they were yesterday. So, I decided to trigger the flow from the end-user Tool rather than doing a test or re-submitting an old one. I did this twice: once for a flow that would meet the conditions and once for a flow that would fail the conditions. It seemed to have run correctly. I'm going to keep an eye on this but I expect there's still something wrong, I just got lucky today. I'm wondering if I'm not extracting/using the data extracted correctly like you said, maybe with regards to the related table aspect. I will keep you posted.

I put the two attributes in separate Compose actions and entered those as the inputs in the Condition. Still have the same issue. Then I thought I understood incorrectly, so I updated the Compose action to the length(output(....)), but that threw an error in the Condition. I'm referencing two separate attributes from the For each. I want to create a record in an Enterprise feature layer, but only when the conditions are met (first condition: Attributes/polytoHDP is changed to 'Yes' and if the Attributes/pacopied is not 1, meaning this action hasn't been done previously). I don't know if I can get the source JSON (how do I find this?) but can't share any data as this is being used with private information.

Thanks for the input. I did try the length version prior to this, but I tried again just in case. That part seems to work, but the other conditions don't. See the screenshot. I looked for the Composes action, but all I could find was Compose, and I have no idea how to enter a condition into the inputs there. See the other screenshot. Suggestions?

I have been working with a couple of people from the PA Team and they suggested I create a Flow that runs automatically to make sure the connections don't time out. Not sure if that will help here, but it might be something to try? Create a new Flow, use "Recurrence" as the trigger, and add the layer(s) below the trigger (I have both ArcOnline and Enterprise layers in my Flow). I've attached a screenshot of mine.

‎05-12-2026

All, I have a Flow that is supposed to copy geometry and attributes from an ArcGIS Online hosted feature class parent record and attributes from a related record to an Enterprise hosted feature class. It is triggered by changing an attribute in the related table. After the record is copied, I have added a step to the Flow to populate a field in the original related table as '1.' This is used in a condition to prevent duplicate copies if the original geometry or attributes are edited in the future. The problem is sometimes the Flow works. Other times Power Automate says "Your flow ran successfully" but it doesn't actually finish; it gets to the Condition step and spins. In the Run results it shows that there is an error, but "The expression contains dynamic functions, variables or parameters that cannot be resolved in the debugger." The Power Automate team suggested I try adding another condition to check if the returned array is not empty. However, I've tried several and it still doesn't work. See the attachment. The team is currently working on a release and can't get away to help and suggested I post here since I need immediate assistance. The function I entered into the window is: empty(outputs('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['body/items']) Sometimes this function doesn't have an error associated with it (the screenshot shows an exclamation point, but some of my trials don't result in the exclamation point), but the others still do. Any suggestions? This is really affecting my workflow and will affect it even more because my Tool will see increased use in the near future! Annina

‎04-27-2026

Thanks for the suggestions! Both don't work so I'm contacting support. I'll update the post when I receive a solution!

‎04-22-2026

All: I have a survey (created using Survey123 Connect) I launch from a URL in a pop up. I have configured the URL to include parameters to automatically populate survey responses. This has been working for a while (1+ years?) but just noticed that a couple of the questions I have included parameters for aren't being populated. They are in a group in the survey, are integer field types, and the source and destination field names are the same. The parameters are in the middle of the URL; parameters before and after work fine (including other questions in groups). The data even display in the URL but they don't show in the survey fields. I've tried the following: Clearing browser cache Re-publishing survey (from Survey123 Connect) Changing all fields in the source hosted feature layer in the web map to not use thousands separators (not just the fields I'm having trouble with) Submitting the survey even though the fields aren't completed to see if they might populate the table (they don't) I've attached screenshots of part of the URL and the portion of the survey where it should be written. Note: I have the "Enable Draft Mode" setting turned on due to random submission failures. This needs to stay on. I have tried resetting the page and it still doesn't populate. Any ideas or if this might be a bug with a workaround? Annina

‎03-13-2026

I am trying to configure the time slider in an ArcOnline web map on the USA NAIP Imagery: Natural Color (Imagery Layer (collection)). All I can see is either the first or the last image year, depending on whether the "Reverse the order" option is toggled on. The only reason I mention this is that I've tried all different combinations of settings but only one image is displayed. It was super easy in ArcPro to configure the time slider on the same service... Any help is appreciated!

‎03-12-2026

Thanks, @ToddW_stl, for the reply. I'd like to highlight that it erases everything from your phone, so make sure you do the back up step!

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by AnninaRupe1

Re: PA Flow Intermittently Working: Condition Error

Re: PA Flow Intermittently Working: Condition Error

Re: Feature layer choices in Trigger end at "N" and I can't select my needed layer

Re: PA Flow Intermittently Working: Condition Error

Re: Feature layer choices in Trigger end at "N" and I can't select my needed layer

Feature layer choices in Trigger end at "N" and I can't select my needed layer

Re: PA Flow Intermittently Working: Condition Error

Re: PA Flow Intermittently Working: Condition Error

Re: PA Flow Intermittently Working: Condition Error

Re: ArcGIS Enterprise Connector Randomly Broken?

PA Flow Intermittently Working: Condition Error

Re: URL parameters stopped working, partially

URL parameters stopped working, partially

USA NAIP Imagery Time Slider Configuration Help

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: Field Maps App Immediately Crashes

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