No longer have REST access to non-public feature layers

RhettZufelt

Before the "update", one could go to the item details page of a hosted feature layer, and either click on the View or copy the URL that takes you to the rest services for that item.

 

Now, if you click the view, rather than taking you to sampleserver#..., it takes you to your organization page with the item id, but can't navigate anywhere else.

 

If you copy the url and paste in a browser, it will at least take you to the REST server, BUT, will not pass any token data anymore, and will only show feature layers that are shared to the entire public.

How do I get to the REST service endpoints for services that are not share publicly, but rather to owner and/or organization?

 

Thanks,

R_

 

 

SFM_TravisBott

Piling on here as this was an important change. 

I am attempting to add a field to a feature service that has a view. The previous workflow was to add the field, then go to the REST endpoint for the view's feature layer, change visibility from 'false' to 'true,' reset the edit date, and apply the update. This would allow the added fields to cascade into the view. But now there are not admin rights on the view layer's endpoints and the workflow if failing to produce the same results. 

Edit - won't get rid of this comment, but discovered that it's still possible there's just a different order of operations.