Publish Feature Services

A feature service provides the as-built features stored in the geodatabase. In other words, it is the existing network that designers tap into, and it is the network into which new designs are pushed.

Once published, the service URL is copied into Solution Center so that Feeder Services can utilize the service. See the topic Create Operational Map From Feature Service for more information about uploading the service URL.

The feature service is created in ArcGIS Pro. When creating the map, keep the following in mind:

• The map needs to include all feature classes which will be edited in the application, including related features such as support structures, surface structures, risers, and conduits.

• The map also needs to include all the related object tables that store related records/units. Even though these are not spatial, Feeder Services still consumes the related record data.

• There should not be any duplicate layer names in the Table of Contents.

  • Duplicate layers with different definition queries are allowed. Ensure they are named differently in the Table of Contents.

• Features in the service are eventually mapped and referenced in the Schema. For this reason, ensure the feature names in the Table of Contents are clear and not potentially confusing.

• All feature services use the same Schema. There are not separate Schemas for different feature services.

• Any Geodatabase Regions (GRRs) created are not for a specific feature service. Instead, they are for the tenant as a whole.