What is project validation?

Mobile Project Center provides a project validation function that verifies project integrity issues such as a missing project extent and incorrect field settings. The validation function runs automatically when a project is saved, but you can also run it manually at any time. The purpose of running validation against your current project is to make sure there are no potential issues when the project is deployed to your field devices.

There are two categories of project issues: errors and warnings. If errors exist in a project, it will not function correctly; if warnings exist, the project will function but with less usability.

Using the Validation function in Mobile Project Center

When you save a project (File > Save or File > Save As), the Validation function runs automatically. You can also run it manually by clicking Project > Validate in the main window. The Validation Result panel appears and lists the identified issues (if any).

When validation is complete, the Validation Result panel appears at the bottom of the window. The panel has the following two tabs:

• Errors and warnings—This tab describes the identified issues as well as the severity, source, and code of each. Mobile Project Center can fix some issues using default actions. For example, if you didn't set the project extent, Mobile Project Center can set it to the full extent. You can access the quick fix tool by right-clicking an error or warning, then selecting the suggested solution for a fix.
• Detail—This tab gives detailed information about the issue (such as the name of the map layer and the field that caused the issue), as well as a solution on how to fix the issue.

When you fix an issue using the quick fix tool, the issue is automatically removed from the Validation Result panel. If you fix the issue yourself, you can re-run the Validate function to verify that the issue has been fixed.

Severity of project issues

Mobile Project Center organizes potential issues into the following severity groups:

• Error —If you save the project without fixing these issues, the project may not work correctly.
• Warning —Issues that can cause loss of usability or functionality if not corrected, but can be addressed for best case workflow.

Sources of project issues

Errors and warnings are categorized by their sources. This information helps you identify the component of your mobile project that caused an issue. The types of sources, and a general solution for each, are described in the following list, but you can get more details about an issue using the Detail tab:

• Project extent—The project extent is not set or is set partially or totally outside of the full extent of all map layers. Use Project > Project Extent to fix (see Creating a mobile project for details).
• Spatial reference—Spatial references among all mobile map layers do not match. Remove the layers with mismatched spatial reference to fix.
• Map layer fields—A field caption is missing or a required field is marked as non-editable. Select the layer, then fix the issue in the Fields tab (see Configuring map layer fields for details).
• Project tasks/capabilities—The caption of a task or capability is missing. Fix this in the Tasks or Capabilities tab on the left panel.
• Project identity—Settings of the project identity layer are incomplete or incorrect, or the identity layer is absent but other layers have fields auto-filled by identity information (see Configuring project user identity for details).
• Logging—Auto-fill settings of logging or field crew are incomplete (see Configuring logging and field crew layers for details).