Select to view content in your preferred language

Error previewing layer ... AGOL permissions issue?

2003
12
12-22-2023 07:30 AM
MichaelRosen1
Occasional Contributor

I have a few public facing AGOL applications which I've wrote over the past few months.  For no obvious reason (*), none of them work now because my account seems to no longer have permissions to creates hosted feature layers.  Layers I previously created still show up as content but post a "Error previewing layer / Layer preview no supported for secured feature services.".  Like this:

MichaelRosen1_0-1703258445178.png
The organizational account I'm using has Admin privs:

MichaelRosen1_1-1703258518216.png



According to the documentation, (and consistent with my recollection of what I actually did some months ago), to create Feature Layer I should:

1) Create a new feature layer in ArcGIS Online.

Login to your ArcGIS Online account, and in the My Content section, you can click the Create Layer button to create a new hosted feature layer. 

However, I don't have a "Create Layer" button there.  Instead, here's what I get when I got to My Content / New item (+):

MichaelRosen1_2-1703258831564.png

No "Feature Layer" here.  Why not?

(*) One suspect is that I recently installed the "Tree Management Solution".  It's was not what we need and I uninstalled it. 



 

12 Replies
NiraArcgis
Emerging Contributor

We're also seeing this same issue starting yesterday. It's the exact same problems that Michael has outlined. 

MichaelRosen1
Occasional Contributor

So, good news and bad news here guys!

Good news is that the problem has gone away.   I appreciate whoever did whatever they did to resolve the problem.

The bad news is that things that go away by themselves come back by themselves and I didn't change anything.  ESRI didn't say they changed anything.  Yet the problem has gone away.  One wonders why this happened, if there is/was anything we can do to prevent it and if it will happen again.  

It would be really wonderful if ESRI would weigh in on this.  Apparently, I'm not the only one it happened to..

JamesD90
New Contributor

I am having the same issue, started just before Christmas but unfortunately it hasn't magically fixed itself for me!

 

I just went into my account to see if anything has changed, but all my hosted feature layers now tell me that "You do not have permissions to access this resource." when I try to see the item details. I am also getting errors trying to load any of them in Map Viewer or Map Viewer Classic, and the app that I built (which is how I first noticed) won't let me access it via the public link, and in editor just tells me there is an error.

MichaelRosen1
Occasional Contributor

Timing for me, JamesD90 and NiraArcGIS all coincide ... mid December 2023.  It's fixed for me now.

Here's the way my "New Item" (Content) dialog shows up.  Note that there the Feature Layer and Tile Layer are back (compare my earlier screenshot where these were missing).

MichaelRosen1_0-1704333253378.png

 

MichaelRosen1
Occasional Contributor

I spoke to soon.  While I can create feature layers now, I'm unable to share them publicly.  It's disabled.  There are references to this related issue. (scope of api key).  That does nothing for me.  I'm dead in the water here.

This all worked fine a month ago.  I really need ESRI to weigh in.

MitchellFasanya
New Contributor

Any luck yet @MichaelRosen1 ? Same issue here. Not sure when it started. Stumped.

MichaelRosen1
Occasional Contributor

Nothing.  It's been at least two weeks; there's strong reason to think that this is on ESRI's end and there's no obvious way to get them to respond here.  I'm looking at other options.  Frustrating.  Sorry.

Djizibizy
Emerging Contributor

Hi,

I don't have a solution but i have the same problem since two weeks without improvement. I have just opened a ticket too.

https://community.esri.com/t5/arcgis-online-questions/hosted-feature-layer-doesn-t-work-anymaore/m-p...

We keep in touch

 

NiraArcgis
Emerging Contributor

This magically fixed itself for us too. We don't have to share anything publicly, we only share with specific groups. Maybe that's why it's not an issue for us?