topic Issues with generating token/reading data after update on Wednesday in ArcGIS Online Questions

Issues with generating token/reading data after update on Wednesday

BigLouC — Mon, 30 Jun 2025 15:26:48 GMT

Getting this error from PowerAutomate with web hooks

Unable to process template language expressions in action 'Generate_Server_Token' inputs at line '0' and column '0': 'The template language expression 'decodeUriComponent(first(triggerBody())['changesUrl'])' cannot be evaluated because property 'changesUrl' doesn't exist, available properties are 'name, orgId, serviceName, lastUpdatedTime, events'.

This was working fine Tuesday, Wednesday no more.

I am using webhooks as per this example

https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/use-webhooks-to-automate-workflows-in-arcgis-field-maps-with-power-automate

It now states that its outdated.

So did the update made the above unusable to move us to the new format?

Re: Issues with generating token after update on Wednesday

BigLouC — Mon, 30 Jun 2025 12:38:53 GMT

Now sometimes it dies on the gettoken part, now it dies after parsing edits

InvalidTemplate. Unable to process template language expressions for action 'Apply_to_each' at line '0' and column '0': 'The template language expression 'body('Parse_Edits')['edits'][1]['features']['adds']' cannot be evaluated because array index '1' is outside bounds (0, 0) of array. Please see https://aka.ms/logicexpressions for usage details.'.

did something change in the template after wednesday?

@JoshuaClifford1

Re: Issues with generating token after update on Wednesday

BigLouC — Mon, 30 Jun 2025 14:16:36 GMT

Found the issue.

The update changed the structure if the json coming back after parsing edits

It used to be like this:

"transportType": "esriTransportTypeUrl",

"responseType": "esriDataChangesResponseTypeEdits",

"edits": [

{

"id": 0,

"features": {

"adds": [],

"updates": [],

"deleteIds": []

}

{

"id": 1,

"features": {

"adds": [

{

Where the index for the data was in 1. Now they removed id:0 from the mix, so the index to get the data is no longer 1, but 0. Like below:

"transportType": "esriTransportTypeUrl",

"responseType": "esriDataChangesResponseTypeEdits",

"edits": [

{

"id": 1,

"features": {

"adds": [

I updated the template line 'body('Parse_Edits')['edits'][1]['features']['adds']' to 0 instead of 1 and now it works.

I am not sure if this information was passed on what was updated, I did not see anything mentioned

@JoshuaClifford1