Specific Fields in the Upload Process

All data for uploads is validated according to the same rules that apply when data is input through a WP Issues CRM save/update form. If a field on a record fails validation, the record will not be uploaded. You will be able to see how this is going to go in the validation dialog after you have mapped fields. The validation process occurs on several levels within WP Issues CRM.

For fields that take a finite set of values (for example, address type), you generally can customize those values under Options, but you should do so before you finalize your upload. If a lot of records fail validation because of an uncustomized option set, you can recustomize the option set and revalidate (as long as you haven’t already proceeded to complete the upload).

ID: WP Issues CRM Internal ID — you will only have this if you started with export from WP Issues CRM.
Street Address: Single field like so: 123 Main St, Apt 1. Do not worry about exactly how you punctuate your addresses or how you refer to street (ST, st, str) or apartment. If you choose under Settings, WP Issues CRM can link to the US Postal Services to standardize records when you view them individually. For batch standardization, you will need an outside service.

In Version 3 and up, you have the option of supplying street address components which, if supplied, will be combined to form street address. The components will be separated by spaces, except that:

  • No space will be inserted between parts 1 and 2 (so they could be used for loading from sources that separate street number and suffix — 35 R will be saved as 35R.
  • Part 7 is intended as a “secondary address identifier” — like “unit” or “apt”. If no part 7 is supplied, but part 8 is supplied (and is non-blank), the abbreviation “Apt” will be inserted before part 8. The address will be unpunctuated (following US postal standards).

Note: You do not need to use the component parts in a consistent away across uploads — different sources split address different ways. You also do not need to use the components consecutively — you might load just components 1, 5 and 8, for a random example.

State: WP Issues CRM does not care how you abbreviate or do not abbreviate state — but it will enforce the definitions you define under Options. Note that you will be able to default state for your entire upload under the Set Defaults tab.
Zip: If Verify USPS Zip Format is set under WP Issues CRM Settings, Postal Code will be validated for 5 or 5-4 character format. Note that you will be able to default zip for your entire upload under the Set Defaults tab. On the constituent form (but not for the upload process), you can configure postal address checking which automatically standardize address format and supply zip code.
City: City is not validated. Note that you will be able to default city for your entire upload under the Set Defaults tab.
Email Address: Email Address, if supplied, must be valid. Validation is through PHP’s FILTER_VALIDATE_EMAIL filter. According to the PHP Manual, “In general, this validates e-mail addresses against the syntax in RFC 822, with the exceptions that comments and whitespace folding are not supported.”
Phone Numbers: Non-numeric characters in phone numbers are dropped on save to the database. When showing a phone number in a form or report, WP Issues CRM will reinsert formatting for 7 or 10 digit phone numbers (if appropriate).
Dates: WP Issues CRM accepts most standard date formats (using the php DateTime object) and date formats can vary within a column. Completely invalid dates will reduce to a blank and be treated as errors.
Gender: You can set any gender coding you wish under Options. You will need to do so before validating your data — codes that have not been set as options will lead to record rejection.
Deceased 0 for living. 1 for deceased.
Address, Email, Phone and Activty types: You will be able to use any existing type codes in your upload by setting Options and/or you can accept default settings for these fields.
Status types: You will be able to use any existing status codes you have by setting Issue/Case Status Options.
Issue: This field must be a valid numeric issue/post ID from your WordPress database (if you specify it). It must point to an issue that is open for activity assignment.
Issue Title: If you specify issue titles that do not exist, you will have the option of automatically creating new issues — see Set Default tab. However, if Issue is supplied, it always overrides Issue Title for matching purposes. When creating issues based on title, the activity assignment status is not checked. Blank titles are not valid and will generate an error.
Issue Content: Issue Content is only used if (a) Issue Title is mapped; (b) Issue Title is not overridden by an Issue setting; (c) You affirmatively elect under Set Defaults tab to add new issues.
Pro/Con You will be able to use any existing Pro/Con or favorability coding that you set up under Options.

Leave a comment

Your email address will not be published. Required fields are marked *