Electric/Gas Feature Services with Separate Push DB

The previous topics regarding the Electric and Gas Options show the default configuration where the application pulls and pushes components from the same geodatabase. In this configuration, you need only one Network Feature Service.

There is an optional configuration to pull components from one geodatabase, but push components back to a different geodatabase. For example, you might have a design database that acts as a temporary “sandbox” for your work. After you push the design to this sandbox, other team members at your company or your company WMS take it from there and finish the design process. In this configuration, you need two feature services: the Network Feature Service to pull components and their attributes into Designer XI and the GIS Push Feature Service to take the new design components from Designer XI and push them back into a different geodatabase.

Default Push-to-GIS Version

In addition to the GIS Push Feature Service, there is one more field to populate: the Default Push-to-GIS Version. When the edits are pushed back to the separate geodatabase, they are pushed into an Esri version (not into a Session Manager session). Thus, this field needs the version to use when pushing edits.

Layer Names and Field Names Must be the Same Between Feature Services

Both published feature services use the same schema.xml file. Thus, the layer names for the included feature classes and their field names must be identical between the two published services. Further, all fields in the schema.xml need to be present in both feature classes in the two published services. In other words, a field cannot be missing in one feature service and present in the other. The field needs to be present in both feature services.