Sure, so here's the body, following along with this walkthrough:
So there's got to be something related to the body provided in that walkthrough?
Here's my body, from this walkthrough:
{
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"layerId": {
"type": "integer"
},
"orgId": {
"type": "string"
},
"serviceName": {
"type": "string"
},
"lastUpdatedTime": {
"type": "integer"
},
"changesUrl": {
"type": "string"
},
"events": {
"type": "array",
"items": {
"type": "string"
}
}
},
"required": [
"name",
"layerId",
"orgId",
"serviceName",
"lastUpdatedTime",
"changesUrl",
"events"
]
}
}
When I replace with your simple body above, it works!
So it must be something about the body from the walkthrough? Of note, as discussed above the walkthrough is for hosted layers in ArcGIS Online, but I'm working against a referenced feature service on a federated hosting server in Enterprise. Possible that the properties called must be different? I don't know where to look for a correct list.
Also, even though you deduced a solution to the first problem, I might ask another question or two of you here because you seem very willing and able to help! So I've been getting run errors in Power Automate in the Generate Server Token Step:
"Unable to process template language expressions in action 'Generate_Server_Token' inputs at line '0' and column '0': 'The template language function 'first' expects its parameter be an array or a string. The provided value is of type 'Object'. Please see https://aka.ms/logicexpressions#first for usage details.'."
This is one other step that was tripping me up in the construction of the flow. I think I have the right URL for server tokens, but I'm not as sure as I am as in the Portal Token step where I'm very confident the URL is right.
Here's what the walkthrough says to add on the body of the Generate Server Token:
f=json&token=@{body('Portal_Token_Response')?['token']}&serverURL=@{decodeUriComponent(first(triggerBody())['changesUrl'])}
So it does use the f/first function, which PA says should be an array or string, but the next parse json step specifically calls for an object schema.
Zach,
My Generate Token looks like the following. This is a bit different from yours. You'll notice I've hard coded a username/password in. I'm not real sure about the errors you're getting.
I'll point out 2 things -- 1) If you make your feature service public, you can probably skip the token. 2) I see you pointing to port :6080 -- this makes use of a self-signed cert that will cause security warnings. PA might not like communicating with something that is not "Secure". Can you point at your fully qualified web adaptor URL?
I've extract my test flow and attached it here as a zip. You can try importing it into your environment. The places you'll need to update:
- On import you'll need to connect it to your 365 account
- Generate token: url, username, password
- Inside "check status until ready", you'll need to update the URI in the Check Status (Click the "concat" and update the URL in the expression)
- Apply to each > Email. You'll need to update the send email address
