Latest Contributions by ZacharyHart

And only EB? That's really good to know. Thanks! ... View more

You may want to check this out. https://community.esri.com/t5/arcgis-for-power-automate-questions/power-automate-fetch-updates-is-not-creating-a/td-p/1324366/page/2#M485 ... View more

@AnthonyLatini @SeanKMcGinnis  Have you guys seen this thread?? ... View more

@AnthonyLatini @SeanKMcGinnis  same here! Have responded over at this thread as well:  Re: Power automate fetch updates is not creating a... - Esri Community ... View more

@MonikaWheat88  Did you ever figure this out? I have spent a while diagnosing this here at the Esri forums as well as MS PowerAutomate forums. I'm not saying this your exact problem, but here's an observation I had. I had a flow working perfectly fine, I hadn't modified save for a few things in the message being put into the Teams channel.  The error is misleading (well at least in this case) as it lead me to believe that the input from the Fetch Updates step based on the same error you received:     The execution of template action 'Apply_to_each_2' failed: the result of the evaluation of 'foreach' expression '@{outputs('Fetch_updates,_changes,_or_deletions_from_feature_layer')?['body/items']}@{body('Fetch_updates,_changes,_or_deletions_from_feature_layer')}' is of type 'String'. The result must be a valid array.     So I went back to my Team channel and looked for the last valid response to make it through. I then attempted to reformat the message output in PA and then the flow suddenly started working again. I don't have an exact before and after but I cleaned some things up and added spaces between each insert parameter in the message. I also didn't change out any of the parameters, like i kept the same editor tracking fields I wanted to see in the message.  This is a complete mystery to me, and since looking at your screen shots, it appears what I have discovered may not help you at all. But there are numerous, unsolved posts about this! This was a false positive. It now appears that there is no discernable correlation between success & failure.  @SarahRijneke I reviewed your post as well; i'm trying  a mix of edits/updates: add new text to string field, modify text in a string field, change the attributed on a coded domain field etc. No pattern has arisen yet. EDIT!: The same flow which I modified and had working fine immediately failed the second time using the exact same test (change to a record).  @AnthonyLatiniHave you seen this thread yet? ... View more

@ColinLawrence This web map contains private client data, while it is noneditable I do not have permission to share this. The other editable data is presumably the only relevant thing from the client side.  ... View more

@NataliyaLys @LaraJuliussonUSFS  I'm having the exact same issue as well. The flow as built fresh today, working fine, and then suddenly started failing without warning.  ... View more

@Faiez Could you expand on this a bit please? are we providing a portal content URL, a service URL? Does this apply to web maps or only hosted feature layers...??? ... View more

Hi @ColinLawrence  I'm getting reports from field staff about the same issues. All have Active Tab 3 with Android 13 and Field Maps 23.3.0. The reports I'm receiving are for both GPS averaging and line streaming. I'm trying to gather more details metrics so please let me know if you are looking for any specifics. ... View more

Thanks for this Elisabeth! I'm curious about the disparity between AGO in Pro in the implementation of Arcade regarding dictionaries now. ... View more

Ok new clues. I'm going to mark your other response as the solution since it got us to where we need to be, but the rest looks like we have found a potential bug.  A colleague tested for me and the expression works just fine in AGO. For the heck of it, I saved a copy of that layer in AGO with the working label expression and brought it into Pro. Labeling failed to work. Checked the expression and same error about field not found. I tried to add Expects($feature, "Type") and that returns a new error of invalid JSON. So everything works fine in AGO but there's a problem with this solution in Pro. Thanks for everything!  ... View more

I noticed that and i'm still getting the same error about field not found. Perhaps this is an issue with the label expression builder? I'm trying to fetch attributes with that interface. (ArcGIS Pro 3.1.3) ... View more

I should have mentioned I tried that as well but when doing this I'm given an error of field not found. I know the format for Arcade attribute labels is $feature.fieldname  var stuff = { "0": "SCC", "101": "SEP", "4": "CLT", "23": "CGS", "8": "CTR", "7": "CTH", "14": "DSW", "9": "ECT", "5": "FTH", "21": "GPS", "10": "GSL", "3": "ITH", "22": "ITS", "13": "ISH", "20": "OSR", "17": "PTC", "26": "PCT", "24": "SAL", "18": "STC", "15": "SWR", "19": "STR", "6": "TFA", "12": "3SS", "11": "2SS", "100": "GPE", "25": "WHI", "102": "RET", "103": "TSI", "104": "POL" }; var keyField = "Type"; // Look up the value based on the key from the field var lookupKey = $feature[keyField]; var lookupResult = Dictionary(stuff)[lookupKey]; return lookUpResult; ... View more