Layers are unchecked in Pro, but visible in Portal Map Viewer

[AmyRoust]

I have a colleague with an issue I am unable to replicate. They have a Pro project set up with ~10 layers, some of which are visible by default and some of which are not. When they publish the map as a feature layer, the visibility settings are ignored and all layers are visible by default. Have I just never noticed that this is a "feature" of publishing registered services in Enterprise 11.3 or is there a setting somewhere that I am handling differently than them without realizing it?

[CodyPatterson]

Hey @AmyRoust

This is consistent with what I'm seeing as of Pro 3.5.2, I published a map with around 10 layers as well, and with a random assortment hidden, and they all uploaded as visible, maybe this was just something I had ignored in the past, but my way of dealing with it was changing the visibility settings when added to a map. If you need multiple maps with this, you may need to save the map, and then use "Save As" duplicating the map itself.

I suggest possibly posting this as an idea to investigate, that may bring out the reason this isn't supported or get this on the developers radar!

Cody

[Eugene_Adkins]

That's not normal behavior. Sounds buggy if this behavior started with an update.

In the past I have only noticed this behavior if a new field was added to the feature service's origin aprx, or if the order of the map's layers were changed and the service was updated with the overwrite option. Though when the last circumstance applied, the pop-ups for the features were also negatively affected by showing the associated data in the wrong fields due to the order of the layers being changed. I have also noticed in the past, if you have any attribute rules applied to a field, this can change the behavior of the other fields if they are not all published as visible.

Good luck.