Latest Contributions by KevinHibma

Sync is not currently supported with ArcGIS Enterprise Hosted Feature Service webhooks. We have an enhancement to add support. However, adding this level of support comes with some technical challenges, as such, I can't offer any sort of timeframe of when/if we'll achieve this. ... View more

The Survey123 connector is not part of the new Enterprise connectors (this is why you don't see it mentioned). You can see the high level "buckets" in Power Automate where S123 is it's own entity. I'm not on the Survey123, nor the team developing the Enterprise connectors (I come from core webhooks in Enterprise), so at the risk of saying something incorrect, my understanding is the S123 connector is hardwired to connect to ArcGIS Online and will only find surveys in there, thus they cannot use this connector for Enterprise. Looking at your guide - you have specific instructions on an Enterprise connection to S123: I've never seen this before, and I don't see it now while looking through PA. Perhaps my knowledge is out of date, or my subscription doesn't have the correct access. Apologies if I've posted some incorrect information. Please do correct me if I'm wrong. ... View more

Unfortunately feature service webhooks are not available in ArcGIS Enterprise 10.8.1. They were added in 11.1 The suggestion to use the Survey 123 webhook could possibly work if that made sense for your workflow: using a survey to submit a record. Otherwise, you don't really have any options in 10.8.1 Enterprise to listen for new features short of deploying a custom server object interceptor (SOI) Edit -- I missed the fact this was posted to the Survey 123 community, so I'll guess that you are indeed using Survey123. Without testing myself, I believe this should be possible. The connectors in Power Automate are great: they make it really easy to setup connections, but almost everything those connectors provide could be manually setup. Inside Power Automate, if you start your Flow with When a HTTP request is received -- this listens for incoming webhook payloads. Save your flow, you'll get a webhook URL, copy that, and then manually add it into the Survey123 webhook payload URL. After that you'll need to build out the logic in Power Automate to parse the respond and get the information you're after. ... View more

Hi - Unfortunately at this time, only the Organization webhooks can be sent directly to Notebook Server. Enhancing Enterprise Feature Service webhooks so they can direct payloads to Notebook Server is on our roadmap, however I cannot predict when we'll implement this functionality.  You've identified the middle-ware workaround of sending to Power Automate or Make and having them send off the request to the notebook. Alternatively, if you've exposed your Notebook as a WebTool, you might be able to direct the webhook to this endpoint. I'm mostly confident that the webhook would trigger the tool (notebook), the problem becomes getting the payload contents which I don't believe can be handled. So if the notebook could go and do something without information from the payload, this might be a solution for you? ... View more

What type of Feature Service are you using? If you're using ArcGIS Enterprise with a referenced feature service (your data is coming from an Enterprise Geodatabase): yes, the server generation numbers are time based as you mention. If you're using a hosted feature service (same for both Online and Enterprise), the server generation numbers are incremented through transactions, but have no relationship to actual time values. To the best of my knowledge, the values for a hosted feature service are only "refreshed" (incremented) any time an edit happens. Assume your feature service had 0 edits over a 12 hour period: the values should not increase. Contrary, if you had hundreds of edits in the same time period, you would see a large jump between numbers. ... View more

A few questions? What version of ArcGIS Enterprise are you using? Are you using Organization or Feature Service webhooks? Some background information: Organization webhooks do not use the challenge/hash method as referenced in the help link. They use a straight keyword which is included in the payload that the receiver can use to decide if the payload is trustworthy. Enterprise Feature Service webhooks made use of the same pattern as the Org webhooks in 11.0 (Beta) and 11.1. That is, the keyword sent in the payload. Beginning at 11.2 (just released), the Enterprise Feature Service webhooks were updated to match Online Feature Service security model, sending a signature hash in the header based on a given keyword/payload itself. This update matches the security model your referenced in the doc. For Enterprise Feature Service webhooks, you can see the doc note here indicating this change happened in 11.2: https://developers.arcgis.com/rest/enterprise-administration/server/create-webhook.htm As you said you're using Flask (Python), if you want some code that does the CRC/Hash/Signature workflow, you can see the code I have here: https://github.com/Esri/webhooks-samples/blob/master/Developer/azure/function.python/Hook/__init__.py and https://github.com/Esri/webhooks-samples/blob/master/Developer/azure/function.python/Hook/hash_check.py - This code was developed for Online Feature Service webhooks, but you pull the functions out, putting them into Flask and applying them to Enterprise 11.2 Feature Service webhooks ... View more

Today, ArcGIS Online does not support Organization webhooks (as found in Enterprise). Online supports webhooks on Feature Services and Survey123. I know they have this request officially logged (I cannot find the tracking reference right now). As far as I know, there is no planned date date to implement Organization webhooks in Online; it's still in the research phase. ... View more

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

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

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

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

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