FAQ: What Changes Are Automatically Reflected in a Referenced Map/feature Service?

What is a “referenced” service?

A referenced service is one that points directly to a dataset in an registered enterprise geodatabase, such as an SDE feature class in SQL Server. When published from ArcGIS Pro to ArcGIS Enterprise, it does not copy the data; instead it references the live data source. This allows for dynamic updates of certain types of changes.

Which changes to the data or layer are automatically reflected in a referenced service?

Automatically Reflected Changes
Add or delete features
Editing existing attribute values
Modifying geometry (move, split, reshape, etc.)
Schema changes (adding/removing fields in the geodatabase)
Updating domain values (if stored in the database)
Editor tracking field updates
Adding/removing attachments

Which changes do NOT reflect automatically after publishing?

Not Automatically Reflected
Adding or removing a definition query on a layer
Changing symbology in ArcGIS Pro
Updating labeling
Editing pop-up configurations
Adding or removing joins/relates
Changing metadata (title, tags, summary, etc.)
Renaming or deleting the source feature class
Removing or changing fields in the map layer only

These changes are considered layer properties, not database changes. They are captured in the service’s manifest at the time of publishing and are not dynamically updated.

Why doesn't removing a definition query in ArcGIS Pro update the feature service?

Definition queries are stored as layer-level properties in the service configuration. Even after removing the query in an ArcGIS Pro project, the published service still applies to the original query unless the service is overwritten. Portal for ArcGIS does not provide a built-in way to edit or remove a definition query from a published layer.

How can we update these non-reflective changes?

You must overwrite the web layer from ArcGIS Pro.

Does deleting the ArcGIS Pro project affect the published service?

No. Once a service is published, it becomes independent of the original project file. Deleting or editing the project does not impact the service unless you explicitly republish or overwrite it.

Summary Table

Reflected Automatically	Not Reflected Automatically
Feature edits (add, update, delete)	Definition query changes
Geometry edits	Symbology updates
Schema changes in the database	Labeling updates
Domain changes (in DB)	Pop-up settings
Attachment updates	Joins/relates
Editor tracking updates	Metadata/title/summary changes

Note:
To reflect schema changes made in the database on the service automatically, ensure schema locking is disabled for the map service, which allows to modification of the referenced dataset's schema without stopping the service. If schema locking is enabled, the map service needs to be stopped to make changes. When the service is started again, it will pick up the schema changes.

Article ID: 000038044

Software: