Latest Contributions by CalvinHarmin

Do we know if this affects all versions of SQL Server? And only SQL Server and not other db’s like postgres? ... View more

Can you describe that license check bug? I haven’t heard of that one yet. ... View more

So are you saying that you are certain the ${numberofviolationnotes} variable is a field in a feature class that is populated/calculated by a Survey123 form? Do you have access to the Survey123 design? Do you know if it was made using Survey123 Connect, or just the standard AGOL Survey123 design tools? ... View more

Hm interesting, I've had the opposite experience -- I've only started using Power Automate ArcGIS connectors a few months ago, and I have had enough issues with the ArcGIS connectors that it was the weakest link in my whole solution and caused me anxiety and time spent tracking down fails and (re)processing things. It thankfully did force me to increase my error handling strategy. But it's been 2-3 weeks since my rewrite without the ArcGIS connectors for querying/updating features, and so far none have failed whereas I would have experienced something on the order of 10-20 fails in the same time period before.  ... View more

Doh I see it now! You covered all the bases 😁 ... View more

I also highly kudos the methods @abureaux mentioned.  I will add this: it is extremely helpful to include the Flow Run URL in the email you send yourself so you can one-click jump to that flow history and see what failed. The method get this URL is thankfully very simple. Just put this in a compose or variable or just plug the expression into your email action directly.  concat('https://make.gov.powerautomate.us/environments/', workflow().tags.environmentName, '/flows/', workflow().name, '/runs/', workflow().run.name) Replace 'https://make.gov.powerautomate.us/environments/' with whatever your own power automate domain is.  That will be the direct URL to review that specific flow run.  FYI this is the raw output of the workflow() expression. The concat() expression above just grabs the relevant bits to assemble the flow run URL correctly after your power automate domain.  {     "id": "/subscriptions/cc97105b-731d-474d-b89d-251e6750824e/resourceGroups/05B5E599E0E84C08A2129FA883E62107-75C096716CAFE86D98E4DB2EC4DC0B17-ENV/providers/Microsoft.Logic/workflows/af484700-3606-4385-8c8c-c1fe190fdf2c",     "name": "af484700-3606-4385-8c8c-c1fe190fdf2c",     "type": "Microsoft.Logic/workflows",     "location": "usgovtexas",     "tags": {         "flowDisplayName": "test: arcgis rest API",         "capabilities": "Premium",         "environmentName": "75c09671-6caf-e86d-98e4-db2ec4dc0b17",         "logicAppName": "af484700-3606-4385-8c8c-c1fe190fdf2c",         "environmentFlowSuspensionReason": "75c09671:2D6caf:2De86d:2D98e4:2Ddb2ec4dc0b17-None",         "state": "Enabled",         "createdTime": "7/3/2025 6:38:25 PM",         "lastModifiedTime": "7/24/2025 6:23:00 PM",         "createdBy": "6e1af543-02dd-4eff-979a-c0184fa8e143",         "triggerType": "Instant"     },     "run": {         "id": "/subscriptions/cc97105b-731d-474d-b89d-251e6750824e/resourceGroups/05B5E599E0E84C08A2129FA883E62107-75C096716CAFE86D98E4DB2EC4DC0B17-ENV/providers/Microsoft.Logic/workflows/af484700-3606-4385-8c8c-c1fe190fdf2c/runs/08584482255021274964740499500CU62",         "name": "08584482255021274964740499500CU62",         "type": "Microsoft.Logic/workflows/runs"     } }   The concat() expression creates this URL: "https://make.gov.powerautomate.us/environments/75c09671-6caf-e86d-98e4-db2ec4dc0b17/flows/af484700-3606-4385-8c8c-c1fe190fdf2c/runs/08584482255021274964740499500CU62" ... View more

I have found ArcGIS connectors unreliable -- lots of authentication errors in the middle of hundreds of other successful runs. This is a separate issue from the 2-week re-authentication issue.  I have changed my use of ArcGIS connector actions to using HTTP GET or POST actions using ArcGIS REST API instead. I'm not sure if this is possible for your workflows but I found it to be more reliable. This relies on getting an AGOL token first to use in the API call. The query output body has a "features" array that contains one or more features (if your query where clause had a match).    Get AGOL token child flow (I use the Solution feature of Power Automate so I can run child flows and have a migration pipeline from a development/test to production environment. Lemme know if you're curious about that). But this all that the child flow is doing -- another API call to get AGOL token:   The actual query API call   Compose attributes of the first result. Or you could do a For Each... action and do something with each feature if you expect to return more than 1.      ... View more

If you "include survey info" option for the webhook, the outputs of the automated webhook trigger from a survey should include most of the attributes, but NOT the standard AGOL hosted feature layer CreationDate and the other "editor tracking" fields. However, you could use the time of the webhook received as the created time, although it may be off technically by 1-3 seconds for the time it took to get the webhook to PA.  If you use Survey123 connect, you can specify in the XLSform that the survey should include the built-in survey "start" and "end" types. You can 'name' these fields to be whatever attribute name you want them to be in the hosted feature layer; these are separate from CreationDate although often the survey "end" (i.e. when user hit the submit button) datetime should be basically the same as the CreationDate time. They do not show up to the user.    The way I do it is I use the webhook as the trigger, but then use the objectid from the survey to query the hosted feature layer for that objectid so I get the 'full' set of attributes, including CreationDate and EditDate. This would be necessary later on anyway if you have a custom field to store an 'edited' datetime instead of using the native EditDate editor tracking field. Lemme know if any of that doesn't make sense I can try to explain further.   ... View more

I'm not sure if this is relevant, but AGOL stores dates as epoch milliseconds. I noticed your math is using 7 days in seconds, 604800. I wonder if you would need to add three zeroes to that, otherwise you are only subtracting 0.007 days? ... View more

I think we need more information: I added a jpeg of a building plan to the satellite imagery, and I published the map. This is too vague I think, can you add more detail about your process? ... View more

I wonder if you might want to use the REST API with an HTTP connector (premium license required) using the GET method. Here's an example of how I query an AGOL hosted feature layer. The REST_url is just the Feature Service or Hosted Feature Layer REST endpoint that includes the /0 on the end to specify the relevant layer id within your service. The output JSON 'body' of this action will have a 'features' value, which is an array. Each item in this array will be the JSON object for a feature that is returned that matches your where query parameters; each of these feature items includes an 'attributes' JSON object and a 'geometry' JSON object. In my case I'm just getting the attributes for a single, specific objectid, so my 'features' array has only 1 item that I need to parse for further processing. But your where query could include both the objectid(s) from the webhook trigger, AND if it matches your Needs_GISupdating = 'Yes' requirement. If there are multiple features, you can create an Apply to Each condition to process each feature or send an email for each feature. Or you can parse each item and append it to an array or something if you want to send one email with information about all of the relevant features at once.  I can try to assist more if you want to go this route to query your data.  "features": [             {                 "attributes": {                     "objectid": 48847,                     "otherattributes": "yada yada"                 },                 "geometry": {                     "x": -8771208.883218553,                     "y": 4241626.251971537                 }             },            {                 "attributes": {                     "objectid": 48849,                     "otherattributes": "blah blah"                 } ... and so on         ]   ... View more

If I'm not mistaken (i.e. in my testing/experience in ArcGIS Pro (I'm on 3.2)), the Field Calculate tool is a kind of 'brute force edit' that will not validate values with a domain before applying updates, both for gdb and AGOL sources. EDIT: I see now that the Field Calculate in ArcGIS Pro has an 'Enforce Domains' parameter you can check. That seems to work for me to prevent writing any value that is not in the domain code list. Trying to write the correct 'description' value will not work, it seems to only allow the code (case sensitive).  ... View more

Thanks for the secondary datapoint, I am planning on doing the same strategy as you. Our survey has a hidden field 'Status' that is populated with 'Submitted' by default; this is changed to 'Received' if my flow runs successfully, and 'Error' if the flow fails for some reason. So I think I can just compare if any record is 'Submitted' and the 'survey_completed_datetime' field (after converting epoch millisecond time to UTC) is more than X minutes from utcNow() then I can consider it an orphan 😞 and needs to be processed. I sure do wish AGOL had some kind of logging. I wonder if they do on the backend that we don't have access to.  ... View more