Edit Data Integrity Check: Check Function Validate PostalCode

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:	Function ''Validate_PostalCode''
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown Yes No
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

Implementation date was earlier than that when we had this in a tmp field; it has been checked for longer than this. Implemented in ''Function Validate_PostalCode()'' and ''Function is_valid_postalcode'' * will reject empty field * will reject invalid postal code (ie not PC Like "[A-X]#[A-Z]#[A-Z]#") === Declined portion of checks === Cross-checks of PC against [[Province]] were implemented at some point but then discontinued due to false positives. ''Function pc_province_match''. Comments in there: ' 2016-07-25 ' it was decided long ago not to check this by the steering committee because ' it gave false positives. ' 2016-11-14 emailed team to find out if we should revisit == Related articles == {{Related Articles}} [[Category:Registry checks]] [[Category:Postal Codes]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel