Hello. I am publishing (overwriting) an existing feature service from Pro (3.0). The attribute table contains fields that are of no value to the end user. In the Fields table, I switched off visibility to all fields except the ones I need in the service and the shape field (required to be visible). The published service had the visible fields, but also had one additional field and the globalid field. As a test, I created a new service (not an overwrite) same settings. Same result. I can control visibility of the fields in the pop-up, but would like to understand why a couple of invisible fields made it to the service. The web map in use was created in the now classic map viewer. I have since saved the web map in the new map viewer and working with the pop-up and fields here. The feature service was removed and reloaded in to the same web map in the new map viewer. Not sure if there is a connection but wanted to include this information. Thanks!
Update, not globalid, but the objectid is visible. Maybe that's required.
The symbology on the service uses the other "invisible" field, so I assume that field needs to be present in the service, else how does it symbolize the points? Sigh.......
Update, not globalid, but the objectid is visible. Maybe that's required.
The symbology on the service uses the other "invisible" field, so I assume that field needs to be present in the service, else how does it symbolize the points? Sigh.......
