|
POST
|
HI there @TimCavins - we are currently working on a fix for this particular issue and have it in our next project plan. There were some underlying issues and infrastructure hurdles that caused a long delay in resolving this issue. Once we have it deployed and in production, I will update this thread. Thank you for your patience!
... View more
09-20-2023
01:14 PM
|
0
|
0
|
1300
|
|
POST
|
Ah perfect! That was going to be my first question to you (are you in the government space), but I see that you edited it in. 😀
... View more
09-20-2023
09:27 AM
|
0
|
0
|
2713
|
|
POST
|
@TL2 - From my testing, I am not entirely sure what issues you might have with 10.9.1. I think under the hood, a great deal of the features and processes should be the same. Meaning, if you are only using CRUD-based operations such as creating, deleting records, etc., then it may work just as well against 11.0 and above. Let me know if you see anything crazy!
... View more
09-20-2023
09:26 AM
|
0
|
1
|
2714
|
|
BLOG
|
@TL2 - While different instances of ArcGIS Enterprise may work (meaning anything below ArcGIS Enterprise 11.0), we only officially support ArcGIS Enterprise 11.0 and above.
... View more
09-20-2023
09:23 AM
|
1
|
0
|
3350
|
|
POST
|
@TL2 @ZenMasterZeke - That is correct! There are some differences between the Survey123 connector and the ArcGIS Connector. I have made a post around the latest changes in the ArcGIS Connectors for Power Automate connector. Take a look here. As a note, the ArcGIS Connector only works with ArcGIS Enterprise 11.0 and above. If you are looking to connect using the Survey123 connector directly, then I would recommend reading through this setup guide. How To: Create an ArcGIS Survey123 Connector for Microsoft Power Automate for Use with Arc (esri.com) Let me know if this helps!
... View more
09-18-2023
07:43 PM
|
1
|
5
|
2760
|
|
BLOG
|
Configure layer in ArcGIS Enterprise to allow editing To begin, you must enable the feature layer to allow editing. If the layer does not have these options enabled, the webhook and updates will not work. Log into your ArcGIS Enterprise portal Navigate to the location of your feature layer and select it Select the layer that you want to enable editing on Click Settings from the ribbon Scroll down to the Feature layer (hosted) section and enable the following options under Editing: Enable editing Keep track of changes to the data Under the What kind of editing is allowed section, enable the options applicable to your flow The settings will save automatically Configure trigger (automated cloud flow) in Power Automate Next, we need to configure the trigger in Power Automate to obtain the HTTP POST URL. In these steps, a flow will be configured to listen for changes to the feature layer. Create a new automated flow Name your flow and then select Skip The following trigger is not in the auto-generated list when creating a flow In the Flow editor, search for the following trigger and select it: When an HTTP request is received In the Request Body JSON Schema, paste the following JSON into the field: {
"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"
}
},
"required": [
"eventType",
"when"
]
}
}
}
} Add a new action and search for the ArcGIS Enterprise connector Under the list of actions, select Fetch updates, changes, or deletions from feature layer (Preview) In the Get changes from field, select the chnagesUrl from the dynamic content list Select the layer that is needed for the webhook flow. This should be the same layer you edited in the first section of this walkthrough. By default, all the options that can be used as trigger are set to true. You can change these options based on the type of flow you are creating. Save the flow. After saving, the trigger will autogenerate a URL. This URL is needed for the next steps and configuring the webhook in ArcGIS Enterprise. After saving, you should have a flow that looks like this: Keep this tab open as the HTTP POST URL will be needed for configuration steps in the Enterprise organization Configure feature layer with webhook URL This section will go over the steps necessary to create a webhook on the feature layer you are using for your flow. Prerequisite: You must be signed in as an administrator on the Enterprise organization to process the next steps. Navigate to the following URL: https://organization.domain.com/server/admin/login When the page loads, you should see the following screen: In a new tab, open the following page: https://organization.domain.com/portal/sharing/rest/generateToken The following page appears: Type in the administrator’s username and password Under the Client section, ensure that Wepapp URL is selected and type in the following URL format: https://organization.domain.com:443/server/admin Set the expiration to any of the options in the dropdown. The default is one hour. Once all the fields are filled in, press Generate Token Copy the Generated Token from the new field that appears On the previous page/tab, paste in the newly generated token to the Portal token field Press Login Once logged in, select Services from the list of resources Select the appropriate folder where the feature layer is stored. By default, this should be under the Hosted category Select the service you want to add the webhook to When the new page loads, scroll to the bottom of the page Select webhooks From the Supported Operations section, select create On the Create Webhook page, fill in the appropriate information to create the webhook Name: Name the webhook. It is recommended to name this something meaningful to keep track of the webhooks Changes type: By default, a “*” (wildcard) should be entered to retrieve all the changes on the layer. You can specify which changes you’d like if you do not want to capture every action made against the layer. HookURL: This is the URL that was generated from the Power Automate automated flow. Paste the value from the trigger into this field. After pasting the URL, click Create The webhook has been successfully created Create a flow to test the webhook on the feature layer Now that the webhook has been created, we can run a simple test to see if the webhook is listening and capturing changes as expected. A simple test for this is to add a new attachment to a feature layer. Create a new Instant Cloud flow from your Power Automate landing page You can name the new action; however, it is not necessary. This action is meant as a test to see if the webhook is working and can be deleted after the test. Add a new step and search for the ArcGIS Enterprise connector Select Add attachment from the list of actions In the action window, select the layer that contains the webhook For Record ID, type in an ObjectID or unique identifier from your feature layer. You may need to show this column in your data table For Attachment name, type in: webhooktest.txt For File content, type in: This is a test. Save and test the flow After the flow runs, the Run History should show that it succeeded Open the Webhook flow to see if the webhook was trigger correctly The Run History should also show a new entry and the webhook process should be successful
... View more
09-18-2023
07:30 PM
|
1
|
13
|
5023
|
|
BLOG
|
ArcGIS Connectors for Power Automate is updated regularly to provide new features, improved speed and usability, and bug fixes. The 2023.3 update is a quality release. Performance improvements, new actions, and bug fixes have been made for the following features. This release will start deploying on September 18th, 2023. It may take up to 48 hours to push out to all regions (up to two weeks for government-level sites). If you do not see the changes, you may need to clear your cache and restart your web browser to see the changes in Power Automate. As always, please let us know of any improvements or issues you want to chat about. --- ArcGIS Enterprise If you had gone to this year's User Conference in San Diego, you might have heard the team mention support for ArcGIS Enterprise inside of Power Automate. Well, it's finally here! We are rolling out the ArcGIS Enterprise connector in phases. The first phase, which is now available in Power Automate, contains all of the same CRUD-based operations that are found in the ArcGIS connector. For example, you can start adding, deleting, or updating records and attachments in your feature layers just as you would using the ArcGIS connector. The second phase of the ArcGIS Enterprise connector will contain the remaining actions that pertain to geocoding, geoenrichment, and networking. We are also working on adding webhook support for ArcGIS Enterprise 11.2 and above. In the current phase of the connector, you must manually set up the webhook on your feature layer. Details on how that is done can be found in here. Note: This is a preview action as support for webhooks will not be fully integrated until the release of ArcGIS Enterprise 11.2. Some notes about the ArcGIS Enterprise connector before I move onto the next topic. Requirements: - The ArcGIS Enterprise connector supports ArcGIS Enterprise 11.0 and above - To use the webhook preview, you must have ArcGIS Enterprise 11.1 or above - Your Enterprise instance must have access to the internet (or at least access to Power Automate itself). The connector will not work behind a firewall or in a disconnected environment. All of the set-up information can be found here in our documentation. Documentation: Set up the ArcGIS Enterprise connector—ArcGIS for Microsoft 365 | Documentation Find Address Candidates As we have been working through various flows and feedback from you, a common ask was having the ability to use custom geocoders in the geocoding actions, Find Address Candidate and Geocode Addresses. By default, those two actions return the top match from the ArcGIS World Geocoding Service, and you can pass those values into another action or application. Dynamically, it will only return the top result. For example, when I geocode 15 Maple Street, I receive the best match after the flow has finished. I deliberately did not pass any other information other than the street name. As a fun note, this is one of the most common street addresses in the United States. In the results, it appears that the World Geocoder gave me a location in England. Even the score that was returned isn't 100 (meaning it wasn't a perfect match). Now let's pass that same variable into the new action Find Address Candidates. The first difference in this action is the ability to change the geocoder. This list is populated dynamically from your ArcGIS Online (and eventually Enterprise) organization. For this example, I will still use the ArcGIS World Geocoding Service. When I use the same address, the results window looks a bit different. In this result, it is now sorted by the Top candidate. If I peek at the raw outputs, I can see that there are multiple results for this address. From this action, I can now pass either the top candidate or create a flow that filters out the results based on a score of 80 or above. I encourage you to play around with this action and use it in your flows as it will open up some new possibilities with custom geocoders in your organization. Token Expiration / Manual Sign In A workflow that was a huge hurdle to overcome in ArcGIS Connectors for Power Automate was manually refreshing your connection whenever the token expired. For example, if your organization had a 14-day timeout on your login, you would need to manually refresh the credentials to keep your flows active. That is no longer the case and has been implemented since early May 2023. We have been running internal tests and have confirmed that even with a token timeout of 90 days, as long as you run a flow with the same credentials, the token will refresh automatically, and you won't need to sign in manually. Attachment Support While this has been in the connector for a bit of time, I wanted to highlight it here in this post. Added support for the use of Attachments in ArcGIS Connectors for Power Automate Attachment Triggers When an attachment is created When an attachment is deleted When an attachment is updated Attachment Actions Add attachment Query attachment Get attachment Delete attachment Get attachment from URL ---- Bug fixes and polishes Bug Fixes Fixed a bug related to the Get geometry from feature layer action - Exporting to EsriJSON does not return the correct values Fixed a bug related to the Fetch updates and changes actions - Fetch updates do not filter results to the selected Feature Layer Fixed a bug related to CRUD operations for feature layers - Create a record fails when only "Add" is enabled in settings Fixed an issue where Fetch updates, changes, and deletions was returning unexpected changes in the results body Fixed an issue related to triggers failing for certain layers Fixed an issue related to inconsistency in runtimes in longer flows Fixed an issue when a flow contains empty geometry and would not complete Fixed an issue when updating a record requires a “number” but is a “string” Fixed an issue when a query returns no records even with the appropriate query parameters Fixed a rare issue with Create a feature layer when a layer added to ArcGIS Online would merge data fields together UI/UX polishes Fixed an issue where the watermarked text was not appearing for Ring Buffers under the Geoenrichment action Quality of Life updates Users can now choose what editing options they want available for their feature layer. Previously, it was required to have add, delete, and update checked for editing. Updated multiple error messages into a human readable format Token expirations are handled by the user's organization and refresh tokens do not need to be manually updated --- The ArcGIS Connectors for Power Automate connector continues to grow and expand. We are working on the next phase of ArcGIS Enterprise support and will be rolling that out in the next few months. We also have been compiling your feedback and are working on some new helper actions and finding ways to make automation fun and exciting. As always, we love to hear your thoughts and feedback on the connector (whether it is positive or negative). We thrive on understanding how you use Power Automate and the ArcGIS Connector inside your organization. Let's make automation part of your group's daily routine!
... View more
09-18-2023
07:04 PM
|
1
|
17
|
4425
|
|
POST
|
Hello @Mitina1997 ! As mentioned by @dcallaghan , you can only create one drive time buffer at a time within the ArcGIS for Power BI. This is the current limit in the component and is set that way due to the infrastructure and ecosystem within Power BI.
... View more
07-21-2023
02:19 PM
|
0
|
0
|
1241
|
|
POST
|
@Anonymous User @LeslieUK - Good afternoon, I am following up on this issue to see if it is still occurring. We have recently released a new version of the map component and this issue might have been resolved. Power BI Version: The latest Power BI Desktop version is (as of writing this post) Version: 2.119.666.0 64-bit (July 2023). Please ensure that Power BI Desktop is on the latest version. ArcGIS for Power BI Version: The latest ArcGIS for Power BI version is: 2023.2.187. Please restart Power BI Desktop if you do not see this version listed. Clearing cache: There are a few areas where cache can be cleared for Power BI Desktop. The following steps are meant for Power BI Desktop (not PBI Desktop Report Server). If you are using Report Server, I can provide those steps later on. Please ensure that the cache was removed and cleared from the following locations: On your local system, navigate to the following locations: .exe version—%LocalAppData%\Microsoft\Power BI Desktop (for example, <user>\AppData\Local\Microsoft\Power BI Desktop) Microsoft Store version—C:\Users\<user>\Microsoft\Power BI Desktop Store App Delete the CEF folder. Delete the WebView2 folder. Delete the Cache folder. Restart your machine. Visual Updates: The version of ArcGIS for Power BI is generated through a deployment process via Microsoft's AppSource. In this case, the push is done in the background and downloaded when the new version is available. While your work and report should not be interrupted, there are chances when the upgrade occurs, and Power BI Desktop needs to be restarted. Once you have run through the cache clearing steps and restarting your machine, give the saving process a try again.
... View more
07-21-2023
02:02 PM
|
0
|
0
|
925
|
|
IDEA
|
Hey there @DonTaggart1 ! I think I can help explain what is happening in this scenario and why it is somewhat different when using ArcGIS for Power BI (when compared to say Bing and Azure Maps). When using a filter that is applied to all pages, it will only work when the map is first created. For example, if you set a filter on the page (or all pages) first and then add the map component, it will honor that filter right when the data is dropped. However, if you attempt to filter the map component from another page, this will not work. There are some known limitations within the Power BI environment for third party visuals like our map component. At the moment, this is a known limitation within ArcGIS for Power BI. In the future, we may enhance this feature by adding the option to use the "Filter on all pages" as it would override the default extent that is saved to each map. However, I am going to move this issue to our Ideas board so that we can keep track of it for a future release.
... View more
07-21-2023
01:49 PM
|
0
|
0
|
1063
|
|
POST
|
Hey there @AndrewGalbraith ! Thank you for all of the details in your post. Let's see if we can solve this issue. I would like to double check a few things as well before we proceed. Power BI Version: As per your notes, it states that you are on: Version: 2.117.984.0 64-bit (May 2023). The latest Power BI Desktop version is (as of writing this post) Version: 2.119.666.0 64-bit (July 2023). Are you using Power BI Report Server? If not, and if it's possible, please update Power BI Desktop to the latest version (July 2023). Clearing cache: There are a few areas where cache can be cleared for Power BI Desktop. The following steps are meant for Power BI Desktop (not PBI Desktop Report Server). If you are using Report Server, I can provide those steps later on. Please ensure that the cache was removed and cleared from the following locations: On your local system, navigate to the following locations: .exe version—%LocalAppData%\Microsoft\Power BI Desktop (for example, <user>\AppData\Local\Microsoft\Power BI Desktop) Microsoft Store version—C:\Users\<user>\Microsoft\Power BI Desktop Store App Delete the CEF folder. Delete the WebView2 folder. Delete the Cache folder. Restart your machine. Visual Updates: The version of ArcGIS for Power BI is generated through a deployment process via Microsoft's AppSource. In this case, the push is done in the background and downloaded when the new version is available. While your work and report should not be interrupted, there are chances when the upgrade occurs, and Power BI Desktop needs to be restarted. Once you have run through the cache clearing steps and restarting your machine, give the saving process a try again. If it does not work, please let me know and we can schedule a screen-sharing session to determine what is happening.
... View more
07-21-2023
01:34 PM
|
1
|
0
|
2381
|
|
BLOG
|
@JonDolphin @BrunoGomesdeSouza - Hello! We are currently testing the ArcGIS Enterprise connector in our Preview region. Once we have finished testing, it will be available for general availability. This should be within the next 4-6 weeks as we need to work through Microsoft's submission process. Some notes about the ArcGIS Enterprise connector in Power Automate. We are working on this connector in two different phases. In the first phase, we are supporting CRUD-based operations and a preview action of fetching updates and changes on feature layers. Later on this year, we will be adding support for geocoding, geoenrichment, routing, networking, and webhooks. We will also be working with the ArcGIS Enterprise team to fully incorporate webhooks. Once we have deployed the connector to general availability, we will provide instructions on how to use the preview version of webhooks in Enterprise 11.1 and above. Environments supported: 11.0 and above / 11.1 is required for testing webhooks Actions supported: Note: This screenshot does not include the Fetch updates, changes or deletions from feature layer which will be a preview action. Let me know if you have any questions!
... View more
06-23-2023
10:58 AM
|
2
|
0
|
12134
|
|
POST
|
Good afternoon everyone. I am following up on this thread and wanted to provide a bit of feedback. The Analysis icon will appear on the report page when the report is in Edit mode. If you are creating your report in Power BI Desktop, then this is automatically enabled as Power BI Desktop does not have a Viewer mode. If you are creating your report in Power BI Online, then you will need to click the Edit icon to enable editing/design mode. As a note, we have identified a bug in ArcGIS for Power BI where you might see the following toast message even if your user account is set up properly. To resolve this issue, simply add a new page to the bottom of the report page and tab between them. The toast message should disappear and the analysis tools should appear once you add data to the map. Our team has fixed this bug and will be pushed out in our next release. We are aiming to have our next release in general availability sometime in late July 2023. Please let me know if this helps!
... View more
06-15-2023
02:40 PM
|
1
|
0
|
2237
|
|
POST
|
@Kuyler_JonesCivil - Hello there! My name is Anthony and I am a product engineer on the ArcGIS for Power Automate connector. I was looking over this issue and I would like to help out if I can! We have just pushed a number of fixes earlier this afternoon that should resolve this issue. Please let me know what happens when you attempt to recreate or run this flow again. Below is an example using a table in an action and having it succeed. You should be able to save the flow without any issues now.
... View more
02-16-2023
02:30 PM
|
0
|
2
|
3252
|
|
POST
|
Hello @ahargreaves_FW ! My name is Anthony and am a product engineer on the ArcGIS for Power Automate team. I wanted to give an update on this issue and fix. We have pushed a fix to ArcGIS for Power Automate and all tests have been completed. You should be able to run your flow again and see the correct behavior. In some cases, you might need to recreate your flow (Power Automate can be a tricky environment with caching, etc.). As a note, I tested this using both email responses message in Teams. Further, I also tested this using some "extreme" flows where I was updating, deleting, and creating records all within a 30 second to 5 minute timeframe. I wanted to recreate the original flow as well as some extended testing. Please let us know if you are seeing the original behavior that you posted or if there are any other issues that pop up!
... View more
01-09-2023
04:48 PM
|
1
|
1
|
4145
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-11-2024 03:46 PM | |
| 2 | 09-04-2024 11:54 AM | |
| 1 | 08-27-2024 02:47 PM | |
| 6 | 08-15-2024 02:19 PM | |
| 1 | 08-15-2024 08:02 PM |
| Online Status |
Offline
|
| Date Last Visited |
12-13-2024
08:23 PM
|