Unable to update web layer in ArcGIS Pro

1142
2
Jump to solution
02-12-2019 07:52 AM
JayHodny
Occasional Contributor III

Hello.  I am working with Esri's My Elected Representatives solution in ArcGIS Pro.  I added the ElectoralDistricts feature service to the map project and updated some of the field values. I have two other feature classes added to the project also.  In the past, the Share As Web Layer and Overwrite Web Layer options were visible in the (right click) TOC menu option to Share, but now they are greyed out.  The same behavior is occurring for the two additional feature classes which are sourced from the Pro project's filegeodatabase.  I saw one post regarding spaces in the layer names possibly being a cause.  I renamed one layer (removed a space) in the feature service, but the change did not resolve the issue.  Further, I have everything shared Publicly, and now I am getting a credential prompt whenever I try to view the application from an external environment.  I suppose I could start over and create a new Pro project, pull in the ElectoralDistricts and copy over the two feature classes into the new project filegeodatabase, etc., but I am hoping to hear a better solution from the GeoNet community.  Thanks in advance!

0 Kudos
1 Solution

Accepted Solutions
JayHodny
Occasional Contributor III

I removed and replaced the two feature services in question and rebuilt the web map as a work around, all the services cooperated again.  However, the app was still asking for credentials.  I discovered that I had not shared a custom basemap I created (a grey version of the National Geographic basemap) correctly.  Once I changed the sharing, the app performed as expected when accessed from the public side.

View solution in original post

0 Kudos
2 Replies
JayHodny
Occasional Contributor III

I discovered I can use the Share as Web Layer and Overwrite Web Layer at the ElectoralDistrict feature service level, but not at the individual layer level (e.g., Polling Places, Voting Precincts, etc.).  I am not sure if I could publish at that level before.  However, I am still unable to publish the two feature classes sourced from the project's geodatabase.

0 Kudos
JayHodny
Occasional Contributor III

I removed and replaced the two feature services in question and rebuilt the web map as a work around, all the services cooperated again.  However, the app was still asking for credentials.  I discovered that I had not shared a custom basemap I created (a grey version of the National Geographic basemap) correctly.  Once I changed the sharing, the app performed as expected when accessed from the public side.

0 Kudos