POST
|
Hi @Scott_Sambell - I have replied to your private message. For those using FME, another contributor on the forums posted this response as a fix for FME.
... View more
|
1
|
0
|
47
|
BLOG
|
@Scott_Sambell - Hi there. I am not too familiar with FME. Can you post a screenshot in a private message to me so I can take a look?
... View more
3 weeks ago
|
0
|
0
|
776
|
BLOG
|
@NigelCharman - Ah thank you for that! I will edit my post. I think it saved an earlier draft. Good catch! 😀
... View more
3 weeks ago
|
1
|
0
|
783
|
POST
|
@CESPEDESLUISITD @NataliyaLys @MichaelTorbett @fitzpat_s @Scott_Sambell - Good evening, all. Thank you for your patience on this issue. We have found the root cause of the issue and I have detailed it in the following post. I have written a post about this located here with a quick fix until it is patched by the ArcGIS Online team: 8/15/24: Update and quick fix for issues with Webh... - Esri Community
... View more
3 weeks ago
|
5
|
2
|
320
|
BLOG
|
There have been multiple reports here on the forums and Support issues logged for a recent problem with webhooks not working. We have been searching for the root cause of this issue over the last two weeks and have found the problem as well as a quick solution. In short, a change was made in the underlying ArcGIS Online system which inadvertently affected webhooks not just in Power Automate, but in other client applications as well. This change made it so that 202 responses were no longer accepted in the webhook API and only accepted 200 responses. If you had recently created a webhook, it might have appeared working about 5 to 6 times before it turned off. The results on the admin page for your feature layer might have looked something like this: Once the webhook reached its threshold of unsuccessful events, it would turn the webhook status to false. This would then stop your flows from triggering and running subsequent actions. Currently, a patch is being worked on to resolve this issue in the ArcGIS Online system. Please note that we do not have an ETA on when the patch will be pushed, but we will monitor this closely. However, we have a quick solution to get your flows up and running again. You only need to edit your flows once even after the patch has been deployed. Please see the steps below. Thank you for your patience on this issue as we work through it! ---- In Power Automate, navigate to your existing webhook flow Open the flow and click “Edit” Add a new action right after the trigger Search for Request in the action search box Select “Response” from the search results In the Response action, the “Status code” should be defaulted to “200” Save the flow Navigate to your feature layer in your organization Scroll to the bottom of the page and open the service URL In the upper right corner, click on Admin At the bottom of the page, click on “Web Hooks” Next, select “Activate all” to ensure all of the webhooks are set to True Click on "Activate all" to enable all webhooks. The flows in Power Automate should now start to run again
... View more
3 weeks ago
|
5
|
12
|
1192
|
POST
|
Hello @MatanBenYishay @CodyPatterson ! This is a great post and is on our project boards for our upcoming release in November. Once it is released, you can make use of the ArcGIS Connector (PaaS, Online, Enterprise) and reverse geocode your values. When I have tested this thoroughly, I can provide a preview of a flow that contains the new actions. Keep an eye out on this thread for updates! 😎
... View more
4 weeks ago
|
2
|
2
|
186
|
POST
|
Hiya! So for this error, you may need to modify the application that was created in your ArcGIS Enterprise instance. Please ensure you have the following URIs set in the application in your content. Also - I am assuming that you are on Enterprise since it is asking for redirect URIs. 😀 https://global.consent.azure-apim.net/redirect https://global.consent.azure-apim.net/redirect/arcgisenterprise https://global.consent.azure-apihub.us/redirect/arcgisenterprise
... View more
4 weeks ago
|
0
|
0
|
472
|
POST
|
Hello @TL2 @NataliyaLys @michael_vetter @NigelCharman @CESPEDESLUISITD - Thank you for posting this information. We have a number of reports of this issue and are attempting to pinpoint the root cause of this error. As a note, there have been gradual rollouts of the ArcGIS connectors over the last few weeks with the last of this phase being the ArcGIS Enterprise connector. The ArcGIS connectors started this process during the week of the 2024 User Conference (roughly July 17th, 2024). We are trying to determine if there is a correlation between this deployment and the issues that everyone in this thread is experiencing on July 31st since that would put it at a 14-day token expiration period. Please bear with us as we try and solve this issue! Thank you for your patience!
... View more
4 weeks ago
|
2
|
1
|
613
|
POST
|
@First_Environment - Thank you for reaching out! Can you please provide additional information on this much like @Bloomers3166 has done? Particularly the version of Power BI Desktop, what is on your map, if you have cleared the cache, etc. Thank you!
... View more
07-11-2024
10:26 AM
|
0
|
1
|
940
|
POST
|
No worries at all @Bloomers3166 ! Thank you for the detailed response! This helps quite a bit. One thing that I would like to do for troubleshooting purposes is to ensure you are on the latest version of Power BI Desktop. As of writing this message, the latest version is: Version: 2.131.901.0 64-bit (July 2024) As per Microsoft guidelines (which we follow as well), the version of Power BI Desktop should not be more than one month out of date. There have been multiple updates from Microsoft (including the update of our icon) from April to now. I am wondering if the version is incompatible with what is on Power BI Online. Also, I would like to confirm that you do not have two versions of Power BI Desktop on your machine. In some cases, you might have the Microsoft Store version as well as the .EXE version. There can be some conflicts with updates and sending information into Power BI Online. Ensure that you only have one version installed and that you are on the latest version. Clear the cache in both Power BI Desktop and Power BI Online and then republish the report. Give this a try and let me know what happens!
... View more
07-11-2024
10:25 AM
|
0
|
2
|
940
|
POST
|
@Bloomers3166 - Hey there! Just posting here since I saw you posted a new topic. I have replied there! Thank you! ArcGIS GIS in PowerBI sign in button does nothing ... - Esri Community
... View more
07-10-2024
11:53 AM
|
0
|
0
|
678
|
POST
|
@Imperfect0007 - Thank you for reaching out about this issue! Were you able to add these layers to the map as a Standard user? If so, only feature layers are available for Standard users. When you sign in as an ArcGIS user, you will have access to more options including Tile Layers.
... View more
07-10-2024
11:48 AM
|
0
|
0
|
114
|
BLOG
|
@Roland_at_Planet - I have posted in this thread for a bit more information. Thanks! Reference: Re: Drill button not working with last update from... - Esri Community
... View more
07-10-2024
11:25 AM
|
0
|
0
|
1115
|
BLOG
|
@BrettMartin1 - I apologize for the inconvenience that the update has caused for your reports. For this update, we had to make some changes to how we process the Table of Contents and the technology that was being used. To satisfy both the technology requirements and the multiple requests for a Legend on the map, we did our best to cover any and all scenarios where the Table of Contents were docked to the report. The Table of Contents in previous versions was meant to run as a pseudo-legend; which didn't really achieve what a true legend does from a GIS/cartographic standpoint. In this update, we've now given users more flexibility to have either a Legend or the Table of Contents depending on the content of the map and how the report was generated. To reiterate, I apologize for the disruption this has caused. For future updates, we will be better about upcoming changes to the components. Thank you for the feedback!
... View more
07-10-2024
11:24 AM
|
1
|
0
|
1116
|
BLOG
|
@hgaignard @BrettMartin1 - Thank you for reaching out on this issue! Because of the complexity of this update, there is a chance that there is something cached in the WebView2 and Cache folders in Power BI Desktop and in Power BI Online. This error when signing in is caused by the cache. Please run through the following steps to clear the cache. Reference: Clear the browser's local storage—ArcGIS for Microsoft 365 | Documentation On your local system, depending on how you installed Power BI, browse to one of the following folder 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.
... View more
07-10-2024
11:20 AM
|
2
|
0
|
1120
|
Title | Kudos | Posted |
---|---|---|
1 | Tuesday | |
5 | 3 weeks ago | |
1 | 3 weeks ago | |
5 | 3 weeks ago | |
2 | 4 weeks ago |
Online Status |
Offline
|
Date Last Visited |
Tuesday
|