The issue arises because the standard database view is based on the base table of the points feature class, which does not include edits made in child versions. To resolve this, the database view must reference aversioned viewto reflect changes in the Default version.

1. What Is a Versioned View?

Aversioned viewis created when a feature class is registered as versioned.

It allows querying and editing versioned data, including edits made in the Default version and child versions.

A standard database view does not account for the Adds and Deletes delta tables used in versioning, which is why edits are not visible.

2. Why Alter the View to Use a Versioned View?

By modifying the standard database view to reference the versioned view, the published web layer will reflect changes made in the Default version, including ongoing edits.

This ensures that updates to the points feature class are visible in the web layer without requiring manual intervention.

3. Why Not Other Options?

Have All Editors Reconcile and Post Points Edits to Default:

While this ensures edits are moved to the Default version, it requires continuous manual reconciliation and posting, which is impractical for a frequently edited dataset.

Rebuild Indexes and Calculate Database Statistics on Points:

These actions improve query performance but do not address the core issue of the standard view not reflecting versioned edits.

Steps to Alter the View:

Identify the versioned view associated with the points feature class. It typically has a name like points_EVW.

Modify the SQL for the existing view to reference the versioned view:

CREATE OR REPLACE VIEW points_web AS

SELECT FROM points_EVW;

Update the web layer to use the modified view as the data source.

Test the web layer to confirm that edits made to the Default version are now visible.

References from Esri Documentation and Learning Resources:

Versioned Views in Enterprise Geodatabases

Publishing Data from Views

Conclusion:

To ensure edits made to the points feature class are visible in the web layer, thedatabase view should be altered to reference the versioned view, which accounts for edits in the Default version.