If your organization's needs require a level of data validation beyond what is available by default in Max, you can perform custom configurations. For best results, complete these configuration steps after you test and run initial sync, and before you configure and test real-time sync.

Data validation is accomplished on the Max platform in several different ways. For the simplest and most common validations, you can enable or configure predefined metadata at the field and data type levels. For more complex validation requirements, you can develop custom validations at the record, field, and relationship levels.

Custom validation at the record level is triggered by an operation configured in Object Validator records that are related to specific records of various object types. Multiple operations can be triggered through this relationship to perform various custom validations, with validation errors and warnings captured in a separate object. At the field level, you define custom validation by creating an Operation record that you then relate with the field. Only single operations can be triggered through this relationship. At the relationship level, you can configure a Relationship Validator record to trigger custom validation whenever records of two specific types are linked or unlinked. You can configure a confirmation message to appear if warnings are generated when dispatchers create or update appointments.

Predefined validations are available for fields and data types. In the Field object, you can set the Required flag to make the field mandatory, so that records cannot be saved if the field value is null. You can also set the Immutable flag to make the field read-only after it is populated during record creation. Additionally, each Field has an associated Datatype object. Each data type has an associated Datatype Options record that supports a variety of predefined validation mechanisms. To enable and configure these field options, the Active flag must be set in the associated Field Options record.