The validation process checks if the data in EDI is considered to be valid for entry into thankQ. Any data which fails to pass validation will be flagged with a validation error and blocked from being entered into thankQ until the error is fixed.
Validation has the following rules associated with it:
•Some validation checks can be turned off or ignored for certain Configurations.
•Validation only runs on records that have an Import Status of 'New', 'De-duped' or 'Updated by User'.
•When validation is run a stored procedure will validate the data in the records in all import tables, checking the following:
oData Types - Data must be able to be converted to the correct type, for example it will check if you have not put text in a number or date field.
oData Length - Data must not be longer than the length of the field in the thankQ database.
oValidation will check Validation Rules to ensure that any custom validation rules such as mandatory fields are verified.
oValidation will check Value Ranges (configurable in Lookup Values)
oValidation will check for Duplicate records within the same import (for example if you enter a payment with the same Receipt Number twice in the same import). This process is distinct from checking duplicate records within thankQ itself.
•All validation failures will have the record set to 'Validation Failed'. If a contact record failed to import all of the related records for that contact such as the payment, pledge, membership, etc will not be imported until the contact validation issue is resolved.
•If a record is validated successfully, it will have status of 'Validated' and will be allowed to proceed to the next stage.