Select to view content in your preferred language

Functionality Errors Since AGOL October 2025 Update

304
5
Jump to solution
4 weeks ago
ClaireSullivan
Emerging Contributor

Is anyone else having issues with the GeoAnalytics library (specifically reading and writing to AGOL) since the recent AGOL site update? I am running a notebook I've been running for a couple months and last week I had the following issues:

- basic overwrite broke the existing layer

- all proceeding creates and overwrites (to new layers) have continued to load the same ~49,000 features until the tool breaks 

- As of today, I am unable to read any features into MS Fabric (Profile has admin privileges but I tested on layers I own to double check) 

Let me know if anyone has found any work arounds or run into this as well! 

 

0 Kudos
1 Solution

Accepted Solutions
DerekGourley
Esri Contributor

Hi Claire,

Thanks for sharing all of this information.

The general availability release of GeoAnalytics for Microsoft Fabric requires users to authenticate prior to using any of the functionality in the library.  It looks like the GeoAnalytics for Microsoft Fabric library has been updated to the general availability release in your Fabric region. This means that your existing notebooks will not be able to run without authentication.

The following blog post from Sarah goes into more details about authentication and how it works: https://community.esri.com/t5/geoanalytics-for-fabric-blog/geoanalytics-for-fabric-upcoming-changes-...


Thanks,
Derek Gourley
GeoAnalytics Product Engineer

View solution in original post

0 Kudos
5 Replies
DerekGourley
Esri Contributor

Hi Claire,

I just did a test on my end and I am seeing AGOL read and write work in my Fabric notebook with AGOL 2025.3. Can you provide the code that you are using to read/write to AGOL? And please let me know if you are seeing any specific errors?

We are also aware that there may currently be some issues with access to/from Azure environments due to an outage on the Microsoft side. If the problem persists would you be able to try again in a day or so and let us know if the issue is resolved?


Thanks,
Derek Gourley
GeoAnalytics Product Engineer
0 Kudos
ClaireSullivan
Emerging Contributor

Hi Derek! 

I am using this method to read into fabric:

df = spark.read.format("feature-service").option("gis", "myGIS").load(f""+ url +"/0")
 
and this is the error I am getting back: 
 
Py4JJavaError: An error occurred while calling o6623.load. : com.esri.geoanalytics.internal.AuthError: Not authorized
 
This error is new as of Monday, I was successfully reading/ writing feature layers for months with this code/ credentials.
 
Thank you for your help!
Claire
0 Kudos
DerekGourley
Esri Contributor

Hi Claire,

Thanks for sharing all of this information.

The general availability release of GeoAnalytics for Microsoft Fabric requires users to authenticate prior to using any of the functionality in the library.  It looks like the GeoAnalytics for Microsoft Fabric library has been updated to the general availability release in your Fabric region. This means that your existing notebooks will not be able to run without authentication.

The following blog post from Sarah goes into more details about authentication and how it works: https://community.esri.com/t5/geoanalytics-for-fabric-blog/geoanalytics-for-fabric-upcoming-changes-...


Thanks,
Derek Gourley
GeoAnalytics Product Engineer
0 Kudos
ClaireSullivan
Emerging Contributor

I will take a look. Thank you, Derek!

 Have you had any issues with layers breaking using the overwrite function, or the tool continuously uploading duplicate records? I want to make sure these issues are resolved before I purchase the new license. 

 

Claire 

0 Kudos
NoahSlocum
Esri Contributor

Hi Claire, 
We haven't seen any recent issues related to overwrite, or regarding duplicate records. If you are still able to reproduce these issues, could you share more information about your workflow? We would be interested in the geometry type, the number of rows you're trying to write, the number of rows in the layer you're overwriting, and anything else that might help us reproduce the issues in-house. A sample of your data or other data that can reproduce the issues would be even better. Also, if you can share a specific date when these issues started that would be helpful. Feel free to reach out to us at geoanalytics-pes@esri.com to continue this discussion over email if that's easier.

Best regards,
Noah

0 Kudos