Validating the Geodatabase Configuration

Once a geodatabase is configured it is good idea to check to make sure that there are no problems with links between Lucity and the geodatabase. This helps insure that all the expected data will be transfered. To run a check there is a Validate tool within the geodatabase configuration. This tool can either be run against the entire geodatabase or an individual feature class. This tool can also be run against a replica geodatabase, or feature class. However, any errors detected on the replica should be fixed in the DEFAULT geodatabase's configuration.

There are several parts to the geodatabase verification. The first is a verification of the geodatabase setup based on Lucity requirements. If no critical errors are encountered during that verification it will continue to the verification. The second part checks the geodatabase to ensure that the setup is valid based on the geodatabase data structure. It checks feature class names, field names, and field types.

How To Run a Validation check

1. Select the geodatabase connection, OR the feature class to be checked
2. Right-click on the selected geodatabase OR feature class and select the Validation tool
   • If it is a geodatabase the tool will be Validate Workspace
   • If it is a replica geodatabase the tool will be Validate Replica Workspace
   • If it is a feature class the tool will be Validate
3. The tool will immediately begin to run the first part of the validation and results will be displayed in a validation window.

   

   • The first part of the validation is checking the setup against Lucity requirements it checks to make sure the Required and Optional linking fields are all filled out.
   • The results display the Lucity Module name : Feature Class Name. Any messages for a feature class are displayed below.
   • Suggestions are displayed in Light Gray, Warnings in Orange and Errors in Red.
   • If an Error is detected the Validation will NOT continue on to check the geodatabase. The feature class with the error will NOT be able to sync with Lucity. The following message will be displayed

     

4. If the first part of the validation passes the second part of the validation will immediately start and the results will be shown in the same validation window.
   • The second part is checking the configuration between the geodatabase and Lucity it is checking to make sure the specified fields exist in the geodatabase and that the data types and field masks match.
   • The results display the Lucity Module name : Feature Class Name.
   • Warnings are displayed in Orange, and Errors in Red.
   • If an error is detected the following message will be displayed

     

5. The third part verifies that:
   • The configuration can connect to the Feature Service that the feature is configured to work with.
   • Checks to see if the feature class is in the service.
   • Checks to make sure all the linked fields are in the service.
   • If it can't find a field it checks to make sure that the field name entered in the geodatabase configuration has the same case as the actual field name. If it finds a field name that is the same but entered with a different case the following prompt will appear:

     

   • Click Yes to update the geodatabase configuration with the case-matching field name. This will repeat for any fields that it finds problems with.
6. If the Validation Passes the following message will be displayed

   

7. After the Validation is complete it can be reviewed. Users can select and copy the results. They can also use the File menu to Print, Save, or Email the Results to Lucity Support.

   Note: The amount of time the Validation takes depends on whether it is being run against a feature class and the entire geodatabase. If it is run against the entire geodatabase it depends on how many features classes are linked to Lucity.

   Note: Any Errors or Warnings found during a validation of a replica should be fixed in the DEFAULT geodatabase. These changes will automatically update the replica configuration.