Setup: Lucity to Geodatabase

This configuration makes sure that attribute edits that are made to inventory items in the Lucity environment (desktop, web, mobile) are pushed into the geodatabase.

Note: All Agencies using GIS must complete this configuration if they are going to allow Lucity to update the Geodatabase.

Note: There is an older way of doing this using a non-editable Map Service and the Lucity SOE. However, this options should not be used if the agency will be configuring the Lucity Webmap to Lucity integration.

Setup

Feature Service

A feature service is the primary link between Lucity and the Geodatabase. Feature services are map services published through ArcServer that have Feature Access capabilities enabled. The feature service is added to the Lucity connection string in the Lucity Administration tool under GIS > Connection Strings.

• Create the Feature service
  • The map service must contain all of the feature classes that you want to update in the geodatabase.
  • The feature classes must display all of the fields that are configured to link to lucity.
  • It does NOT need any additional Non-Lucity feature classes.
  • This can either be a new map service, or an existing one.
  • This map does not need to be included in any web maps.
  • It doesn't need any special symbology.
  • This map service must use a user account that has edit permissions to the feature classes Lucity will update in the geodatabase.
  • The map service must be pointed to the version that Lucity should update.
• Open Lucity Administration Tool > GIS > Connection Strings.
• Find your connection string that the links to the same data that the feature service does.
• Add the URL for the feature service to the connection string under Edit Map Service URL.

  Users need Lucity admin permissions to access this tool.

Relevant Settings

In the Lucity Administration tool under System > Settings > GIS Edit Integration tab there is a list of settings that affect this integration.

Note: The Use Feature Service instead of Lucity SOE must be set to TRUE.

Alternative Feature Services

It is possible to setup more that one feature service to perform this function. The previous steps explain how to setup the default Feature Service.

• More information on setting up Alternate Feature Services

What this does

When an inventory update is made in the Lucity environment (desktop, web, mobile) the information is stored in the Lucity database. At the same time Lucity tries to connect to the Feature Service (based on the provided url) and the related feature class (based on the geodatabase configuration). If it makes the connection is pushes attribute updates into the feature service, which in turn automatically updates the geodatabase.