POST
|
Hi @bogdanpalade2 - You're attempting to get to updateDefinition from the Server Admin - updateDefinition is in the REST Services Admin, its a very subtle difference. Your URL will look something like SERVER.COM/server/rest/admin/services/Hosted/MyFeatureServiceName/FeatureServer/updateDefinition
... View more
09-20-2023
06:37 AM
|
0
|
1
|
724
|
POST
|
Unfortunately in ArcGIS Enterprise 11.0 when you check the "Keep track of who edited the data" option there, it does not actually update the FeatureService with the required setting. You'll need to manually go into the Rest Admin for the service and update the capabilities to include ChangeTracking using the UpdateDefinition endpoint. eg. https://server.com/rest/admin/services/Hosted/MyFS/FeatureServer/updateDefinition {'capabilities':'Query, Editing, Create, Update, Delete, ChangeTracking'}}
... View more
09-14-2023
09:17 AM
|
1
|
3
|
742
|
POST
|
Matthew, Do you have ArcGIS Monitor installed? I'd like to understand why you're seeing the message on a 15minute interval. I wouldn't have expected to see this logged more often than every 30minutes. For reference, this is the tracking issue number: BUG-000159271
... View more
08-01-2023
01:17 PM
|
0
|
2
|
742
|
POST
|
Sorry, I sometimes take for granted I use the Primary Site Administrator account which allows me to do anything, anywhere (generally speaking). You can use the Portal Gen Token to request a server token, although that becomes a 2nd call trading portal for server. Or you should just be able to use a server token generation call: https://developers.arcgis.com/rest/enterprise-administration/server/generatetoken.htm To answer your question, yes, I believe you should be able to request a token through your web adaptor without any issues.
... View more
07-20-2023
12:46 PM
|
0
|
1
|
985
|
POST
|
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
... View more
07-19-2023
01:21 PM
|
0
|
3
|
1011
|
POST
|
Good to hear. I forgot, I actually have this documented at https://github.com/Esri/webhooks-samples/tree/master/3rdParty/PowerAutomate (I just updated the JSON schema, removing required from all of them). This link would be a good place to start if someone happens upon this thread in the future. I'll try to get a blog out that builds on the initial one, more focused on Enterprise. thanks for working through this, Zach.
... View more
07-19-2023
11:03 AM
|
0
|
6
|
1021
|
POST
|
That's good news Zach! The blog you have is in invaluable walk-through if you're wanting to extract changes out of the extract changes API. There are some small differences between Online and Enterprise, but that blog for the most part should hold up. Looking at that sample JSON, that "required" section concerns me. I wonder if that is Power Automate's way of saying "if the incoming payload does NOT have those fields, send an error response back", and in turn, the webhook cannot create. The benefit to supply a JSON schema into the HTTP request is received sets up the next connectors with what comes previously, basically making it easier to build up the flow. If you want, try this JSON schema. This is specific to Enterprise Feature Service webhooks, without the required parameters. { "type": "object", "properties": { "serviceType": { "type": "string" }, "changesUrl": { "type": "string" }, "name": { "type": "string" }, "id": { "type": "string" }, "folderName": { "type": "string" }, "serviceName": { "type": "string" }, "events": { "type": "array", "items": { "type": "object", "properties": { "eventType": { "type": "string" }, "when": { "type": "integer" } } } } } }
... View more
07-19-2023
08:57 AM
|
0
|
8
|
2774
|
POST
|
Interesting. If I use your URL, I get the same error. I did a little debugging/comparing to a PA url I have and outside of the webhooks, they function exactly the same, so I'm not sure what is different between the URL you have and the one I have. Inside PA, what does your request body JSON schema look like? Can you set it to something very basic, like: { "type": "object", "properties": {} } And ensure the method is either blank or set to POST?
... View more
07-19-2023
07:52 AM
|
0
|
11
|
1763
|
POST
|
If it's on, I've seen this happen once before and can't explain how it "fixed" itself. My suggestion is to turn the flow on / off (maybe Microsoft-Power Automate is in a bad state accepting incoming connections). If that doesn't allow you to create it, delete your When an HTTP request is received from the Flow and bring a new one in, save, make sure it's on, and get a new URL. In both cases, take the URL and paste it into a browser and see that it returns some response, probably like {"error":{"code":"TriggerRequestMethodNotValid","message":"The HTTP method for this request is not valid: expected 'POST' and actual 'GET'."}}
... View more
07-19-2023
07:31 AM
|
0
|
13
|
1767
|
POST
|
Make sure the Flow has been turned on. If the Flow is off, the receiver is unreachable, thus you cannot connect to it.
... View more
07-19-2023
07:04 AM
|
0
|
15
|
1773
|
POST
|
I believe you're correct it was added in 1.6. I'd suggest using at least 2.0 or higher as I know the team fixed some bugs with it. Try this code snippet to create/manage webhooks from arcgis.gis import GIS from arcgis.features.layer import FeatureLayerCollection gis = GIS("https://www.arcgis.com", "username", "password" ) # Find your layer item i= gis.content.search("webhook") # I know I only have 1 feature layer named "Webhook" so I can cheat with the index flc = FeatureLayerCollection.fromitem(i[0]) mgr = flc.manager wh = mgr.webhook_manager wh.create("My WEBHOOK", "https://webhook.site/aaabbb11223", "FeaturesCreated")
... View more
03-23-2023
12:07 PM
|
0
|
1
|
430
|
POST
|
Thanks. That's sort of good news / bad news. I'm still skeptical the patch has caused the issue, but if you've only had the errors since applying the patch, it's now a question of how the communication was interrupted. I'll talk to a couple of colleagues and see if it's reproducible. Unfortunately, you'll see the messages once a minute as Server attempts to re-establish the connection. Please respond back with the result of restarting Server.
... View more
10-07-2022
09:00 AM
|
0
|
2
|
3262
|
POST
|
Hi @DavidColey I don't have much knowledge of that particular patch, but I'm doubtful that it caused the problem. The message is indicating that GIS Server is failing to connect to the required components for webhooks. Are you able to restart the GIS Server? A restart will sometimes fix this problem. Is there any chance the problem was there before you applied the patch and you didn't notice the logs? If so, we'd need to figure out what might be in the way of the connection. (closed ports perhaps)
... View more
10-07-2022
08:02 AM
|
0
|
4
|
3273
|
POST
|
Kim, I've attached a zip file with my progress on this. I'll note it's not quite complete, but offers the code you'll need to perform extract changes. (Specifically, I didn't complete the authentication to ArcGIS.com, the code assumes the service is publicly accessible). I'm trying to support both Online FS webhooks and Enterprise FS webhooks in the same script, so it needs to handle connecting to both. You'll want to start in the agol_receiver.py -- all this does is grabs a JSON value and launches the workflow. In production, this would act as the webhook receiver and handle requests in real-time, but for this, it's just the entry way to test. Inside extractChanges.py you'll see the basic workflow (start at the bottom). I hope this helps. When I get it finished up, I'll add it to the previously mentioned github repo.
... View more
10-05-2022
09:57 AM
|
0
|
1
|
1279
|
POST
|
I'm getting webhooks sent from a couple of different Orgs/FeatureServices I have on arcgis.com. From your screen shot, you have Active:True and accepting any changes ("*"). So everything looks good.
... View more
09-08-2022
01:02 PM
|
0
|
0
|
1351
|
Title | Kudos | Posted |
---|---|---|
1 | a month ago | |
2 | 01-30-2024 10:13 AM | |
1 | 02-20-2024 07:34 AM | |
1 | 02-20-2024 07:16 AM | |
1 | 01-03-2013 10:44 AM |
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|