From 25e3065c006e956fa18309d0101ce3354ed6b1c0 Mon Sep 17 00:00:00 2001 From: Dave Greenberg Date: Mon, 28 Apr 2014 14:15:01 -0700 Subject: [PATCH] CRM-14122 - Clarify contact matching rules for component imports. ---------------------------------------- * CRM-14122: https://issues.civicrm.org/jira/browse/CRM-14122 --- templates/CRM/Activity/Import/Form/DataSource.hlp | 2 +- templates/CRM/Contribute/Import/Form/DataSource.hlp | 6 ++++-- templates/CRM/Contribute/Import/Form/DataSource.tpl | 2 +- templates/CRM/Event/Import/Form/DataSource.hlp | 8 ++++---- templates/CRM/Member/Import/Form/DataSource.hlp | 8 ++++---- 5 files changed, 14 insertions(+), 12 deletions(-) diff --git a/templates/CRM/Activity/Import/Form/DataSource.hlp b/templates/CRM/Activity/Import/Form/DataSource.hlp index f68ea5605a..01fec74265 100644 --- a/templates/CRM/Activity/Import/Form/DataSource.hlp +++ b/templates/CRM/Activity/Import/Form/DataSource.hlp @@ -35,6 +35,6 @@

{ts}TIP - Matching Activities to Contact Records{/ts}
- {ts}CiviCRM allows you to indicate which contact each activity record belongs to using either the unique CiviCRM-assigned Contact ID, a unique External ID which you assign, OR your configured 'strict' Dedupe Rule set (which uses email addresses by default). You must include at least one of these values as a column in your import file. If you are synchronizing (or migrating) contacts from another application to CiviCRM, and that application has assigned a unique ID to each contact, you can import that value into CiviCRM's External ID field. Then you can use that unique key as the 'match to contact' value when importing related data such as Activities.{/ts} + {ts}CiviCRM allows you to indicate which contact each activity record belongs to using either the unique CiviCRM-assigned Contact ID, a unique External ID which you assign, OR your configured Unsupervised Duplicate Matching Rule set (which uses email addresses by default). You must include at least one of these values as a column in your import file. If you are synchronizing (or migrating) contacts from another application to CiviCRM, and that application has assigned a unique ID to each contact, you can import that value into CiviCRM's External ID field. Then you can use that unique key as the 'match to contact' value when importing related data such as Activities.{/ts}

{/htxt} diff --git a/templates/CRM/Contribute/Import/Form/DataSource.hlp b/templates/CRM/Contribute/Import/Form/DataSource.hlp index 0450768bc6..a05272db49 100644 --- a/templates/CRM/Contribute/Import/Form/DataSource.hlp +++ b/templates/CRM/Contribute/Import/Form/DataSource.hlp @@ -41,8 +41,10 @@ {/htxt} {htxt id="id-onDuplicate-title"} - {ts}Duplicate Matching{/ts} + {ts}Matching to Contacts for Inserts and Updates{/ts} {/htxt} {htxt id="id-onDuplicate"} -

{ts}For each import, you can either INSERT new contribution records, or UPDATE existing records. You can not do both types of operations in a single import session. If you are UPDATING existing contributions, you will need to include a unique identifer to match to the existing records. This can be either the CiviCRM-assigned contribution ID, a unique Invoice ID, or a unique Transaction ID.{/ts}

+

{ts}For each import, you can either INSERT new contribution records, or UPDATE existing records. You can not do both types of operations in a single import session.{/ts}

+

{ts}If you are INSERTING new contributions, you will need to include a column in your data file containing the values used to link the contribution to an existing contact. You can use the 'Internal Contact ID', an 'External Identifier' (if you are using those in your contact records), OR the property defined in your Unsupervised Duplicate Matching rule (which is Email Address by default).{/ts}

+

{ts}If you are UPDATING existing contributions, you will need to include a unique identifer to match to the existing contribution record. This can be either the CiviCRM-assigned contribution ID, a unique Invoice ID, or a unique Transaction ID.{/ts}

{/htxt} diff --git a/templates/CRM/Contribute/Import/Form/DataSource.tpl b/templates/CRM/Contribute/Import/Form/DataSource.tpl index 6e06f1bd2e..facf27ff3e 100644 --- a/templates/CRM/Contribute/Import/Form/DataSource.tpl +++ b/templates/CRM/Contribute/Import/Form/DataSource.tpl @@ -44,7 +44,7 @@ {ts}Select 'Individual' if you are importing contributions made by individual persons.{/ts} {ts}Select 'Organization' or 'Household' if you are importing contributions made by contacts of that type. (NOTE: Some built-in contact types may not be enabled for your site.){/ts} - {$form.onDuplicate.label}{$form.onDuplicate.html}{help id="id-onDuplicate"} + {$form.onDuplicate.label}{$form.onDuplicate.html} {help id="id-onDuplicate"} {include file="CRM/Core/Date.tpl"} {if $savedMapping} {if $loadedMapping}{ts}Select a Different Field Mapping{/ts}{else}{ts}Load Saved Field Mapping{/ts}{/if}{$form.savedMapping.html}
{ts}Select a saved field mapping if this file format matches a previous import.{/ts} diff --git a/templates/CRM/Event/Import/Form/DataSource.hlp b/templates/CRM/Event/Import/Form/DataSource.hlp index 27a2d46ca8..90c64544cb 100644 --- a/templates/CRM/Event/Import/Form/DataSource.hlp +++ b/templates/CRM/Event/Import/Form/DataSource.hlp @@ -50,10 +50,10 @@ {/htxt} {htxt id="id-onDuplicate-title"} - {ts}Duplicate Matching{/ts} + {ts}Matching to Contacts for Inserts and Updates{/ts} {/htxt} {htxt id="id-onDuplicate"} -

- {ts}For each import, you can either INSERT new participant records, or UPDATE existing records during the import session. If you are UPDATING existing records (to update participant status after an event, for example), you will need to include a column containing the unique CiviCRM-assigned participant ID to match to the existing record. This value is included whenever you Export participant records from Find Participants. Please note that you cannot use UPDATE if you wish to use the External ID field to match to existing contacts because the External ID links the incoming record to contact, and that contact may have more than one participant registration record.{/ts} -

+

{ts}For each import, you can either INSERT new event registration (participant) records, or UPDATE existing records. You can not do both types of operations in a single import session.{/ts}

+

{ts}If you are INSERTING new participant records, you will need to include a column in your data file containing the values used to link the event registration to an existing contact. You can use the 'Internal Contact ID', an 'External Identifier' (if you are using those in your contact records), OR the property defined in your Unsupervised Duplicate Matching rule (which is Email Address by default).{/ts}

+

{ts}If you are UPDATING existing participants, you will need to include a column containing the unique CiviCRM-assigned participant ID to match to the existing participant record.{/ts}

{/htxt} diff --git a/templates/CRM/Member/Import/Form/DataSource.hlp b/templates/CRM/Member/Import/Form/DataSource.hlp index 063b6d8aa9..c0c87fa1ab 100644 --- a/templates/CRM/Member/Import/Form/DataSource.hlp +++ b/templates/CRM/Member/Import/Form/DataSource.hlp @@ -47,10 +47,10 @@ {/htxt} {htxt id="id-onDuplicate-title"} - {ts}Duplicate Matching{/ts} + {ts}Matching to Contacts for Inserts and Updates{/ts} {/htxt} {htxt id="id-onDuplicate"} -

- {ts}For each import, you can either INSERT new membership records, or UPDATE existing records. You can not do both types of operations in a single import session. If you are UPDATING existing memberships, you will need to include a column containing the unique CiviCRM-assigned membership ID to match to the existing membership records.{/ts} -

+

{ts}For each import, you can either INSERT new membership records, or UPDATE existing records. You can not do both types of operations in a single import session.{/ts}

+

{ts}If you are INSERTING new membership records, you will need to include a column in your data file containing the values used to link the membership to an existing contact. You can use the 'Internal Contact ID', an 'External Identifier' (if you are using those in your contact records), OR the property defined in your Unsupervised Duplicate Matching rule (which is Email Address by default).{/ts}

+

{ts}If you are UPDATING existing memberships, you will need to include a column containing the unique CiviCRM-assigned membership ID to match to the existing membership records.{/ts}

{/htxt} -- 2.25.1