Contact Import Guide - Revision history

Freddy: /* Contact Import Screen (IMPORTCONTACT) */

2019-05-16T15:01:31Z

‎Contact Import Screen (IMPORTCONTACT)

Freddy at 15:29, 7 May 2019

2019-05-07T15:29:52Z

Freddy at 19:26, 10 January 2019

2019-01-10T19:26:00Z

Freddy at 15:38, 24 October 2018

2018-10-24T15:38:24Z

Freddy at 14:09, 24 October 2018

2018-10-24T14:09:41Z

Freddy at 20:41, 17 October 2018

2018-10-17T20:41:01Z

Freddy at 19:40, 16 October 2018

2018-10-16T19:40:50Z

Freddy at 19:07, 16 October 2018

2018-10-16T19:07:22Z

Freddy: /* Contact Import Database Tables */

2018-10-16T19:06:44Z

‎Contact Import Database Tables

Freddy: /* Contact Import Screen (IMPORTCONTACT) */

2018-10-16T19:06:01Z

‎Contact Import Screen (IMPORTCONTACT)

@@ Line 56: / Line 56: @@
 '''Contact Attributes:''' Select any attributes that should be assigned to ALL contact records in the import file.
-'''Overwrite Duplicates''' Selecting this box will attempt to match import records to existing records using the contact full name and the organization Custno. Matched records will update the existing record with data from the import file.  Blank import file fields will not overwrite, or clear out existing data.
+'''Overwrite Duplicates''' Selecting this box will attempt to match import records to existing records using the contact full name and the organization Custno. Matched records will update the existing record with data from the import file.  Blank import file fields on matched records will overwrite and clear out existing data.
 ==Contact Import File Definitions==

@@ Line 70: / Line 70: @@
 '''f4 - LastName''' - Contact last name
-'''f5 - Phone1Num''' - Primary phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+'''f5 - Phone1Num''' - Primary phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####. Phone numbers 1-4 will not import without a valid, corresponding phone code 1-4 specified in the adjacent column.
 '''f6 - Phone1Code''' -  A two-digit code that defines the phone type.  The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
-'''f7 - Phone2Num''' - Second phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+'''f7 - Phone2Num''' - Second phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####. Phone numbers 1-4 will not import without a valid, corresponding phone code 1-4 specified in the adjacent column.
 '''f8 - Phone2Code''' -  A two-digit code that defines the phone type.  The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
-'''f9 - Phone3Num''' - Third phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+'''f9 - Phone3Num''' - Third phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####. Phone numbers 1-4 will not import without a valid, corresponding phone code 1-4 specified in the adjacent column.
 '''f10 - Phone3Code''' -  A two-digit code that defines the phone type.  The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
-'''f11 - Phone4Num''' - Fourth phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####.
+'''f11 - Phone4Num''' - Fourth phone number. The import process will attempt to standardize all 10-digit numbers as (###) ###-####. Phone numbers 1-4 will not import without a valid, corresponding phone code 1-4 specified in the adjacent column.
 '''f12 - Phone4Code''' -  A two-digit code that defines the phone type.  The code corresponds with the PHONECODE rule in Adjutant. Typical examples are OF for office, FA for Fax, MO for Mobile, HO for Home. Check your rule setup to be sure of what should be entered here.
@@ Line 155: / Line 155: @@
 '''PCXREF''' - Each attribute record will also create an entry in this table. The PTABLE value for all of these should be CONTACT, and the TYPE value should match the attribute name from Text1 of the associated attribute rule. The PARENTID and CHILDID values will correspond to CONTIDs from the VCONTACT table.

← Older revision		Revision as of 19:26, 10 January 2019
Line 1:		Line 1:

−	==General Import ~~Template File~~ Notes==	+	==General Data Import Notes==

−	*Template files are typically generated from their respective Import screen using an 'Export Template' button.	+	Refer to the [[Data Import General Information]] page for information and guidance on general import timeline, formatting import templates, as well as how to ensure you are using the most current template information for data imports.
−	*Using the 'Export Template' button from an updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors.
−	*Templates generally (but not in all cases) contain 3 rows of header information.
−	**The first row is generally labelled with f1 through f## and is used to give a consistent column id to ~~each data column. Do not remove this row unless instructed.~~
−	**The second row is labelled with the ~~column data/field name. The values in this row are used~~ for ~~the file mapping screen. Editing these values is generally not needed~~ and ~~may make the field mapping process difficult.~~
−	**The third row (if present) is labelled either with the same values from row 2, ~~or with more detailed field descriptions. The third row is available to create a customer-friendly name for the associated data column.~~
−	***The third row should be removed from the source file prior to importing. It will cause errors since it will be treated as ~~the first import record on the file.~~
−	Import files MUST always be saved as ~~'Microsoft Excel 5.0/95 Workbook (.xls)' format until further notice. The import screens will generate errors if the file type is not correct.~~
−
−	*It is a good idea to ~~perform a Mapping Table Import~~ using ~~a current source list before beginning on any imports. Without a current mapping table,~~ the ~~quality of imports can be compromised. The Mapping Table Import only needs to be run once on a newly set up Adjutant system. It does not need to be run before each import.~~
−	**Export a current ~~list from the Mapping Table Import screen from an updated system (or contact your Implementation Consultant~~ for ~~an updated file).~~
−	**Perform a Mapping Table Import on the target system with the XLS file from the step above.

← Older revision		Revision as of 15:38, 24 October 2018
Line 170:		Line 170:

	[[Category: Address Book]]		[[Category: Address Book]]
−	[[Category: ~~Conversion~~ Guides]]	+	[[Category: Import Guides]]

@@ Line 3: / Line 3: @@
 *Template files are typically generated from their respective Import screen using an 'Export Template' button.
-*Using the 'Export Template' button from an updated system will help ensure that you provide the customer with the most up-to-date import file, and will help avoid errors.
+*Using the 'Export Template' button from an updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors.
 *Templates generally (but not in all cases) contain 3 rows of header information.
 **The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed.
-**The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the mapping process difficult.
+**The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult.
-**The third row is labelled with the same values from row 2, an is available to create a customer-friendly name for the associated data column.
+**The third row (if present) is labelled either with the same values from row 2, or with more detailed field descriptions.  The third row is available to create a customer-friendly name for the associated data column.
 ***The third row should be removed from the source file prior to importing.  It will cause errors since it will be treated as the first import record on the file.
-*Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format (until further notice). The import screens will generate errors if the file type is not correct.
+*Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format until further notice. The import screens will generate errors if the file type is not correct.

@@ Line 102: / Line 102: @@
 '''f15 - Job Title''' - Contact job title
-'''f16 - Address1a''' - Business street address (Address1 line)
+'''f16 - Address1b''' - Home street address (Address1 line)
-'''f17 - Address2a''' - Business suite or office number (Address2 line)
+'''f17 - Address2b''' - Home suite or apartment number (Address2 line)
-'''f18 - Address3a''' - Business additional address details (Address3 line)
+'''f18 - Address3b''' - Home additional address details (Address3 line)
-'''f19 - Citya''' - Business city
+'''f19 - Cityb''' - Home city
-'''f20 - Statea''' - Business two-character postal code
+'''f20 - Stateb''' - Home two-character postal code
-'''f21 - Countrya''' - Business country code
+'''f21 - Countryb''' - Home country code
-'''f22 - Address1b''' - Home street address (Address1 line)
+'''f22 - Address1a''' - Business street address (Address1 line)
-'''f23 - Address2b''' - Home suite or apartment number (Address2 line)
+'''f23 - Address2a''' - Business suite or apartment number (Address2 line)
-'''f24 - Address3b''' - Home additional address details (Address3 line)
+'''f24 - Address3a''' - Business additional address details (Address3 line)
-'''f25 - Cityb''' - Home city
+'''f25 - Citya''' - Business city
-'''f26 - Stateb''' - Home two-character postal code
+'''f26 - Statea''' - Business two-character postal code
-'''f27 - ZipCodeb''' - Home zip code
+'''f27 - ZipCodea''' - Business zip code
-'''f28 - Countryb''' - Home country code
+'''f28 - Countrya''' - Business country code
 '''f29 - Salutation''' - Contact salutation, such as Mr., Mrs., or Dr.
-'''f30 - ZipCodea''' - Business zip code
+'''f30 - ZipCodeb''' - Home zip code
 '''f31 - DefCont''' - Enter a 'Y' in this column to check the 'Default Contact' field.  This will not update the contact name on the organization screen.

← Older revision		Revision as of 19:40, 16 October 2018
Line 162:		Line 162:

	'''RTRESOURCE''' - Similar to USERID, nothing gets automatically created in this table unless you edit and save the Resource screen.		'''RTRESOURCE''' - Similar to USERID, nothing gets automatically created in this table unless you edit and save the Resource screen.
		+
		+	'''PCXREF''' - Each attribute record will also create an entry in this table. The PTABLE value for all of these should be CONTACT, and the TYPE value should match the attribute name from Text1 of the associated attribute rule. The PARENTID and CHILDID values will correspond to CONTIDs from the VCONTACT table.
		+

@@ Line 68: / Line 68: @@
 '''Overwrite Duplicates''' Selecting this box will attempt to match import records to existing records using the contact full name and the organization Custno. Matched records will update the existing record with data from the import file.  Blank import file fields will not overwrite, or clear out existing data.
-==Customer Import File Definitions==
 '''f1 - Custno''' - Adjutant Organization ID for the associated company record

@@ Line 153: / Line 153: @@
 ==Contact Import Database Tables==
-Importing contact records can create records in the following databases:
+Importing contact records can affect the following databases:
 '''VCONTACT''' - Each imported user is assigned a unique CONTID value. This is the keyno. Each CONTID is linked to a CUSTID, which matches the ENTID keyno from the ENT table.

@@ Line 55: / Line 55: @@
 Menu Location: Transaction>>Importers/Exporters>>Address Book>>Contact Import
-[[File:IMPORTONTACT.png]]
+[[File:IMPORTCONTACT.png]]
@@ Line 66: / Line 66: @@
 '''Contact Attributes:''' Select any attributes that should be assigned to ALL contact records in the import file.
 '''Overwrite Duplicates''' Selecting this box will attempt to match import records to existing records using the contact full name and the organization Custno. Matched records will update the existing record with data from the import file.  Blank import file fields will not overwrite, or clear out existing data.
 ==Customer Import File Definitions==