Hello;
I am trying to publish a map image layer from ArcGIS Pro (3.3.1) to my organization's enterprise portal. This layer is meant to be an update and a replacement for a depreciated map image layer and contains most of the same feature classes previously published on the former layer. For some reason, when I attempt to publish the new map image layer, publishing to the same folder on the portal but with a different name, only the feature classes that were previously published with the older layer appear on the new layer.
There are eight total feature classes, each of which is sourced from the exact same geodatabase. All of them contain identically schemed data covering the same geographic area (each feature class represents a year's survey data) and all of them have the same projection. My project is set up to assign unique IDs for web publishing.
I have attempted to publish this map image layer multiple times, and each time the seven feature classes previously published appear safely but the eighth layer, the one detailing the newest data set, does not.
Can anybody give me some clue about how to resolve this issue? Thank you very kindly.
Were you able to solve this issue? I am experiencing the same thing.
Are you (this would also apply to @AlexanderWadePSD’s description) overwriting an existing map image layer? If so, you cannot change the url or the name of the service. These must stay the same to overwrite.
Generally, if you are overwriting but also adding a feature to the image layer, you will need to remove the existing map image layers from your webmap and add the image layer in anew to see the newly added feature. You can add fields to existing features without needing to do this but if you add a new feature, it creates a bit of a different workflow.
If removing the existing map image layer creates an extensive burden you may be able to try this solution from an earlier post. It’s also possible you may be able to use arcgis online assistant if available. But generally it’s a good rule of thumb to remove existing map image layers and then add them anew to ensure proper behavior. This is also working off the idea there is nothing buggy going on.
Hope this helps get it resolved.