|
POST
|
@ahargreaves_FW If you are using ArcGIS Enterprise 11.2 or above you do not need to create an application. Just click create a new connection on the action you are running and it will open the following dialog. Use your Enterprise url without https. and use arcgisforpowerautomate as a ClientID. It should then ask you to log in. Please also make sure that your Enterprise instance is accessible to Power Automate and is not inside a firewall or internal network. Hope that helps.
... View more
06-06-2025
09:42 AM
|
0
|
0
|
1513
|
|
BLOG
|
@ckellow Thanks for your question. I think maybe the example JSON isn't clear enough to understand this, hope following will clarify that. In the Power Automate form for the action e.g. `Update records in a feature layer (batch)` requires you to choose the layer and the unique id field for that layer. According to the layer I am using in the screenshot above it it is `FID`. This is used to identify which features this batch action is going to edit and not the geometry. This means the attributes json must have the uniqueID field as a key value pair. If it is a hosted feature layer then Unique id field is auto generated which could be FID/ObjectID or GlobalID. In the JSON below I am editing the features with FID 1 and whatever the attributes/geometry I need to update. [
{
"attributes": {
"FID": 1,
"objectid": 1,
"name": "REDLANDS COMMUNITY HOSPITAL",
"address": "350 TERRACINA BLVD",
"city": "REDLANDS",
"state": "CA",
"zip": 92373,
"ownership": "Government",
"ntl_rate": "No Different than Natl Rate",
"mortreadmi": 20.7,
"total": 52,
"latitude": 34.03667703,
"longitude": -117.2038564,
"admissiond": 1436572800000,
"GlobalID": "f822cf31-60d3-426d-8589-1c1486b19739"
},
"geometry": {
"x": -13047073.613499999,
"y": 4033727.9189999998
}
}
] On a side note for you to use up Create, update, delete operation with ArcGIS actions in Power automate a feature layer must have editing enabled with Editor tracking on.
... View more
06-06-2025
09:34 AM
|
0
|
0
|
484
|
|
POST
|
@TimLohnes1 I sorry, it is /server/admin/services/webhooks. Access the webhook correct webhook related to your service and check the `Notification Status` or status in the bottom for any errors. I would also ask you to check `Connections` tab in Power automate home page to see if your connection has expired and needs re authenticate. Also, did anything recently changed for this layer? e.g. Ownership/ editing capabilities or was the layer overwritten by some data. Any additional info will help for me to try and reproduce this issue.
... View more
06-06-2025
09:09 AM
|
0
|
0
|
1209
|
|
POST
|
Hi @TimLohnes1, There hasn't been any changes or updates to ArcGIS Connectors for Power Automate in the last week. I am assuming you are using ArcGIS Enterprise connector. Can you check if the webhook is active at the /server/admin/webhooks/
... View more
06-02-2025
12:28 PM
|
0
|
1
|
1295
|
|
POST
|
@AJD I am sorry to hear that. Is there any other information you can provide us to reproduce the issue. Authentication issues in ArcGIS for Power Automate are bit tricky to reproduce and in lot of the case the error it throws comes from Microsoft which is not useful. Normally, ArcGIS Access and refresh token doesn't expire within that small of a time frame. Is your feature service gets overwritten with new data? Or are there any other restrictions on log in?
... View more
06-02-2025
12:25 PM
|
0
|
0
|
1466
|
|
BLOG
|
Introduction ArcGIS for Power Automate is a powerful tool that enables you to automate workflows by integrating ArcGIS with various services. One significant functionality is the ability to add data to feature layers. However, as your data processing needs grow, you might find that migrating to batch operations becomes essential to improve efficiency and manage larger datasets effectively. What are the new batch actions? In 2024.2 release we introduced Batch actions that allow us to add or update multiple features in a single request. The following actions are added to the list Add records to a feature layer (batch) Update records in a feature layer (batch) These actions will take Array of Features as their input. Notice the difference between Update a record in a feature layer Inputs vs Update records in a feature layer (batch) Appropriate JSON structure for the Array of features can be found here. To extract the schema of your Feature layer, access the REST endpoint of your ArcGIS server service and query the features at "/server/rest/services/FeatureService/<layer>/query". For ArcGIS Online, open Item details for the layer you are trying to query under item details and view the URL. Once at the query endpoint form, under Where, use 1=1 (or an OBJECTID you know) with Out Fields set to * and Format set to JSON. If your data originates from sources other than a feature layer, such as Excel or a database where geometry information is stored in a text column, you must rename the column to "geometry" for the Batch actions to recognize it in Power Automate. Alternatively, you can create the required JSON structure using Power Automate built-in actions like Select, Compose, and Parse JSON from Data Operations, which will be useful. Here is a sample JSON structure. [{
"geometry": {"x": 1234,"y": 1234},
"attributes": {"name1": "value1", "name2": "value2"}
},
{
"geometry": {"x": 1234, "y": 1234},
"attributes": {"name1": "value1", "name2": "value2"}
}] Are batch actions right for you? When working with single feature operations such as `Create/Update a record in a feature layer` you typically add one or a few features at a time to your feature layer. This method is straightforward and can be sufficient for small-scale data additions or updates. There is no need to change the existing workflow as there are no performance gains. Using these actions within a "For Each" loop becomes less efficient when handling a large number of records that need to be created or updated. It is advisable to consider migrating to batch actions in the following scenarios: Updating dozens or thousands of records. The flow is set to run frequently with numerous features. Working with feature arrays can be a better alternative to configuring each field in a form for single record actions, particularly when dealing with feature services that contain many fields. Performing copy operations.
... View more
05-22-2025
03:41 PM
|
2
|
2
|
1059
|
|
POST
|
Hi @KathrynWesson, Thanks for your question. What version of ArcGIS Enterprise you are using? Here are a few pointers for using Power Automate and ArcGIS Connectors. In General, Power Automate must be able to access the URL of the layer. Machine you are accessing should not be behind a firewall or an internal network. To use any triggers (webhooks) in the ArcGIS for Power Automate connectors you must be the owner of the feature layer. ArcGIS for Power Automate connectors currently don't support Webhooks with feature layers referenced from an enterprise geodatabase and on map services. Though this functionality is in current development pipeline and we are hoping to release it soon. I hope it answers your questions. Feel free to reach out if you have any specific ones.
... View more
05-12-2025
09:49 AM
|
0
|
6
|
1681
|
|
POST
|
@CMSchelde I am sorry to hear that the email is still not being sent. You mentioned a survey, what trigger are you using to retrieve changes? If you are using `When a record is created in a feature layer` trigger for a survey from Survey123 then I will advise you to switch the trigger to `When a survey response is submitted` and select the survey. I believe trigger is newer to the blog you quoted. Also, is the trigger running? (do you see the runs in PA?) If so can you check what is the response for the `Fetch updates deletes, or changes` action. (you can click the `Raw Output` button to see what is returned) Let me know and I will be more than happy to troubleshoot.
... View more
05-08-2025
07:19 AM
|
0
|
0
|
1330
|
|
POST
|
@JessMiller1 it is probably late to respond on this thread, regardless, were you ever able to get this to work? We have fixed several issues since then and couple others are in the pipeline if you are using a Feature layer with data referenced from enterprise cloud database. Apologies for any inconvenience. If you still see the error, please reach out and we would love to discuss further on the issue. Please remember Power Automate needs access to the resources to create workflows and firewalls can also block them. Secondly, make sure to use `Fetch Change, updates...` right after the trigger to retrieve the change from the trigger/webhook.
... View more
05-07-2025
12:10 PM
|
0
|
1
|
1233
|
|
POST
|
@CMSchelde If you own the layer please try using `Enter value` and paste in the url of the feature layer. Power Automate is sometimes quite slow retrieving the feature layers especially if the list is large. Any ArcGIS trigger must be used with `Fetch updates, changes...` Action right next to it to retrieve the features that are just updated. `Get data from feature layer` action is helpful to query data from the feature layer and not the changes coming in from a trigger. Hope that helps! Let us know if you have further questions.
... View more
05-07-2025
11:57 AM
|
0
|
1
|
1354
|
|
BLOG
|
We are pleased to announce the latest updates and enhancements to the ArcGIS for Power Automate connectors, released in the first week of April, 2025. The released version is 2025.1. This release introduces a comprehensive array of enhancements and bug fixes. ArcGIS Online and Enterprise connectors were released and following updates doesn't apply the ArcGIS PaaS connector. Key Update BUG-000169725: Authentication to ArcGIS Online through ArcGIS Connectors for Power Automate workflows frequently fails and returns the error message, "Authentication failed. Your session has expired." This issue, which affected a significant number of Esri users, has been successfully resolved along with updates to token exchange mechanism the error messaging. This should provide relief for ArcGIS Enterprise 11.3 and 11.4 users who were affected by this. No further actions are required by users. Important Bugs Fixes An issue with the "Update a Record in a Feature Layer" action has been resolved. Previously, a "STRING" Unique ID was incorrectly treated as a "NUMBER," resulting in an error: No item was found that matches the query <fieldname> = <value> … Action name was corrected from “Update records to a feature layer (Batch)” to “Update records in a feature layer (Batch)” BUG-000173694 An error message returns when using the 'Delete a record from feature layer' action with a referenced feature service in the ArcGIS Enterprise connector for Power Automate was resolved. Using the 'Delete a record from feature layer' action with a referenced feature service from ArcGIS Enterprise resulted in the error below, however, the record was deleted from the feature layer. "ResponseSwaggerSchemaValidationFailure. The API 'arcgisenterprise' returned an invalid response for workflow operation 'Delete_a_record_from_feature_layer' of type 'OpenApiConnection'. Error details: 'The API operation 'DeleteItemInFeatureLayer''. BUG-000170950: The problem where leading or trailing zeros were trimmed when inserting a number into a string field while using the 'Create a record in a feature layer' action in ArcGIS Connectors for Power Automate has been addressed. These updates underscore our commitment to enhancing the functionality of ArcGIS for Power Automate connectors, ensuring that users experience a seamless and efficient workflow. We look forward to bringing you more exciting updates and features in the future. Please feel free to reach out and comment
... View more
04-11-2025
01:48 PM
|
3
|
0
|
944
|
|
POST
|
@sonia_ml Thanks for your question. I will relay that question to our Product management team.
... View more
03-28-2025
06:51 AM
|
0
|
3
|
756
|
|
POST
|
@NigelCharmanPre-Prod Thanks for sharing this. I was able to reproduce this when tried using the function null, If I don't pass anything then it creates a null. I am having our developer look at this. If you must make your flow run, try and see if you can pass nothing when the input is null.
... View more
02-28-2025
11:14 AM
|
1
|
2
|
1296
|
|
POST
|
@NigelCharmanPre-Prod Thanks for reporting that. May I know what connector, action or trigger you are using and how are you setting the null? I tried using `Update record in a feature layer` action and it doesn't use those defaults. {
"attributes" : {
"FID" : 231,
"objectid" : null,
"name" : "Updated -test",
"address" : "test - Atlantic Ocean",
"city" : "",
"state" : "",
"zip" : null,
"ownership" : "Updated Test",
"ntl_rate" : null,
"mortreadmi" : 6,
"total" : 876,
"latitude" : 32,
"longitude" : -49,
"admissiond" : null, //Date
"GlobalID" : "47a6a5e9-898a-4628-b8c6-e67d23c443a3"
} FYI, I am not passing anything in a those fields,
... View more
02-27-2025
09:50 AM
|
0
|
4
|
1313
|
|
BLOG
|
We are pleased to announce that we have fixed issue BUG-000174431 where Power Automate was throwing an error code 1000 with the message "Conversion failed when converting date and/or time from character string." Power Automate is now resolved and should be available in production. This fix affects the following actions: Create a record in a feature layer Update a record in a feature layer Even though the input field is text, the epoch entered should be without quotes, e.g., 1740433032729. Other text inputs are possible in the format of MM/DD/YYYY, etc. For specifications, please refer to the Add Features and Feature Object. When the input date is not in the epoch time, it is recommended to use the "Convert date and time format" action. Thank you for your patience and understanding
... View more
02-26-2025
07:55 AM
|
3
|
0
|
483
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 4 | 12-10-2025 01:53 PM | |
| 3 | 11-06-2025 01:31 PM | |
| 1 | 11-05-2025 02:55 PM | |
| 1 | 10-30-2025 10:32 AM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|