Stopping GIS Tasks from updating the Geodatabase

GIS Tasks are typically used to push information from a GIS Feature Class into Lucity. However, in many scenarios that task also will update information on the related GIS Record. If you need to make sure that the Lucity Tools/GIS Tasks do not update the Geodatabase at all you can use the following steps. However, this is not a recommended setup as quite a bit of functionality will be lost.

Limitations

• Lucity tracking fields cannot be mapped (LucityAutoID, LastSyncDate, LastModDate, LastModBy, InLucity).
• The "Only process records modified since last sync" can only use the last sync date on the task (instead of LastSyncDate in GIS), which is not preferred.
• Update Length/Area option cannot be used.
• Number generators cannot be used.
• Spatial relationships cannot be used (except reverse geocode).
• Address fields in GIS cannot be updated during the reverse geocode process.
• System To/From nodes cannot be updated in GIS.
• To/From Street Names for Street Segments cannot be updated in GIS.
• To/From Intersection IDs for Street Segments cannot be updated in GIS.
• To/From Street info for Intersections cannot be updated in GIS.
• Subsegments cannot be created/recreated in GIS for a Street Segment sync.

Configuration

Select a feature class that will not allow any information to come from Lucity.

1. Publish a map service that contains the feature class. Make sure that the service does not have feature editing enabled.
2. Open the Lucity Administration Tool and go to GIS > GIS Services.
3. Add the map service into the list. Make sure the Has Feature Service checkbox is NOT checked.
4. Assign the service
   • If the map service contains all your feature classes and this process will be used to lock down all your layers then add the map service to your Connection String as the Edit Map Service.
   • If the map service contains only this feature class or a smaller selection, then the service will need to be assigned to individual feature classes. Do this in the Geodatabase Configuration using each configurations Edit Map Service tab.
5. Open the Geodatabase Configuration.
6. Select the Feature Class you are configuring.
7. Make sure the Lucity Tracking fields are not mapped. (LucityAutoID, LastSyncDate, LastModDate, LastModBy, InLucity)
8. Make sure the Update Length/Area option is disabled.
9. Delete any attached number generators
10. Delete any attached spatial relationships (except reverse geocode)
11. If steps 7-10 are not complete the task that pushes information to Lucity from GIS will fail.