Layer Missing From Recently Overwritten LRS Service in Portal

[PaulMAlexander]

Recently I have overwritten an LRS service from ArcGIS pro into portal. After it ran, I received the green completion message. When I looked at the service in Portal, the new layer I added to the service appears in the REST API for that feature service as well as the map image layer of the service. However the layer does not appear in the feature layer of the service. If I bring the whole service into ArcGIS pro the layer does not appear, but if I expand the portal service under the portal tab the layer appears and I can drag it into the map with data. It does not show if I bring in the whole service. Any thoughts on why this is happening?

[Laura]

Were your layer IDs in Pro matched to those in Portal when you overwrote it?

[PaulMAlexander]

Yes. They were all the same. The only difference between the old and the new one was a new layer was added to the publishing map and then the service was overwritten.

[lah]

Were you the owner of the service? We have been running into this when people overwrite services that they don't own in portal, even though the users have administrator level permissions. It is really a nightmare and causes a lot of issues. I think this is a bug but have not had time to thoroughly test it and submit to ESRI. For now, we're only allowing owners of items to overwrite in portal.

[PaulMAlexander]

So I am the owner now of the service when I overwrote it, however the original publishing of the service was not done by me. I just took ownership of it recently. Could there be an issue since I did not originally publish the service and just took ownership of it at the portal application level?

[lah]

Yes. We have tried to circumvent the issue by manually reassigning the owner in Portal prior to publishing, and still have issues. 

From what we've noticed, it's only when adding new layers to a feature service. Then a duplicate of the feature service will get created in portal - one under the original owner without the update, and one under the new publisher with the update. This causes maps and apps to get out of sync, and confusion in the portal.

We're at version 11.5.

[PaulMAlexander]

Okay yeah that is exactly what happened when we did. I made the duplicate. 

We are currently using version 11.3

[PaulMAlexander]

Did you find a solution or fix?

[lah]

No, unfortunately. Like I said, I think this is a bug, and I need to submit a case to ESRI - I just haven't had time. I'd recommend getting it on their radar if you're able so that they work a fix quicker.

Luckily we only have a couple people who own content in our portal, so we're able to avoid it for the most part. But if a user left the company, that would also put us in a difficult position.

[PaulMAlexander]

So after some research did find a a workaround for adding the layer to the feature layer of the service when it is missing, even though it exists in the map image layer and the Rest API for the service.

I ended up using AGO Assistant to modify the JSON file of the feature layer of the service. I copied the layer information from the map image layer and then pasted it into the JSON of the feature layer. Made sure that the new ID number matched that of what was in the publishing map for the service. Once I did that, the layer showed up in the feature layer.

Not an ideal solution for the bug, but a potential workaound.