Changes for page Import - How to Import a File

Last modified by caterina on 2021/10/27 16:31

From 3.1 to 2.1 From 6.1 to 5.1

From version 5.1

edited by melanie@one-count_com
on 2016/12/14 14:12

Change comment: There is no comment for this version

To version 3.1

edited by melanie@one-count_com
on 2016/12/06 15:42

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

@@ -1,6 +4,3 @@
--{{layout}}
--{{layout-section ac:type="two_right_sidebar"}}
--{{layout-cell}}
  {{id name="Start ScreenSteps Content"/}}
@@ -8,25 +8,23 @@
  Please refer to Quick Start Guide - User Operations for important information about basic concepts and rules relating to imports and bulk operations.
--=== OPEN THE "IMPORT" WINDOW ===
++=== OPENING THE "IMPORT" WINDOW ===
--**Select USER OPERATIONS from the Main Menu.**
++=== Select USER OPERATIONS from the Main Menu. ===
  [[image:attach:media_1443213231223.png||align="center"]]
--**Click on "IMPORT" in the sub-menu.**
++=== Click on "IMPORT" in the sub-menu. ===
  [[image:attach:media_1443213261172.png||align="center"]]
--
++=== The "Import" window will open, where you begin begin the import process. ===
--**The "Import" window will open, where you begin begin the import process.**
--
  [[image:attach:media_1443213294962.png||align="center"]]
  === IMPORT STEPS ===
--**~1. In the Import window choose your import file using the "Browse" button (1), and select "Upload File" (2).**
++=== 1. In the Import window choose your import file using the "Browse" button (1), and select "Upload File" (2). ===
  [[image:attach:media_1443213396710.png||align="center"]]
@@ -34,10 +34,8 @@
  [[image:attach:media_1406494045151.png||align="center"]]
--
++=== 2. Give your import an Import Title (1), Import Description (2), select a Source Code (3), select the product term(s) from the Product List (4), and select a Product Status. ===
--**2. Give your import an Import Title (1), Import Description (2), select a Source Code (3), select the product term(s) from the Product List (4), and select a Product Status.**
--
  [[image:attach:media_1443549296560.png||align="center"]]
  Note that the product terms are what appear in the list of products (#4 above) in the Import Engine. Because all products have a term(s) and if a product has multiple terms (i.e. a free print subscription and a paid print subscription), each term needs to appear in the "product" list so that a user can be subscribed to that specific term.
@@ -54,10 +54,8 @@
  Below the Product List, you will see a list of any existing Import Mappings (templates), if any.
--
++=== 3a. If using an Import Mapping Template: Below the Product List, you will see a list of any existing Import Mappings (templates). Find the template you wish to use and select "Use" then proceed to Step 5.. ===
--**3a. If using an Import Mapping Template: Below the Product List, you will see a list of any existing Import Mappings (templates). Find the template you wish to use and select "Use" then proceed to Step 5.**
--
  [[image:attach:media_1362667166234.png||align="center"]]
  For information on how to use and/or create mapping templates, see the lessons "How to Use an Import Mapping Template" and "How to Create an Import Mapping Template".
@@ -64,16 +64,12 @@
  You may select to use a template and then modify it by adding/removing fields to be mapped (as described in Step 4.)
--
++=== 3b. If not using an Import Mapping Template: The mapping function is found below the list of mapping templates. Proceed to Step 4. ===
--**3b. If not using an Import Mapping Template: The mapping function is found below the list of mapping templates. Proceed to Step 4.**
--
  [[image:attach:3b.__If_not_using_an_Import_Mapping_Template__The_mapping.png||align="center"]]
--
++=== 4. Proceed to the mapping section and map your fields (either from scratch or by modifying an Import Mapping Template). ===
--**4. Proceed to the mapping section and map your fields (either from scratch or by modifying an Import Mapping Template).**
--
  [[image:attach:4._Proceed_to_the_mapping_section_and_map_your_fields___1.png||align="center"]]
  (% style="text-decoration: underline;" %)**Definitions**(%%)**:**
@@ -99,12 +99,8 @@
  Question Header and CSV Header field names don't need to be identical, e.g. a Question Header may be "Email Address" and CSV Header "Email".
--
++=== 5. DO NOT SKIP THIS STEP – ALWAYS CHECK FOR DUPLICATES! Check the box for the Active Question Header(s) you want to check for duplicates against. ===
--{{error}}
--**5. DO NOT SKIP THIS STEP – ALWAYS CHECK FOR DUPLICATES! Check the box for the Active Question Header(s) you want to check for duplicates against.**
--{{/error}}
--
  [[image:attach:5.__DO_NOT_SKIP_THIS_STEP_--_ALWAYS_CHECK_FOR_DUPLICATES_.png||align="center"]]
  In the screen shot above, the system will check for duplicates against the Email and Last Name fields. A duplicate would be identified when a record being imported has the same email address AND last name as a record already in the ONEcount database.
@@ -119,90 +119,56 @@
  If you are re-importing a list that was exported from ONEcount, e.g. to change data in a demographic field for multiple records, the best field to check against is "User Account Number" (ONEcount ID or ocid) because each user can have only one OCID. (% style="color: rgb(255,0,0);" %)//**Note that at the current time, you can't name a column in your import file "ocid". If you do, the system will give you an error message telling you to use a variation such as "oc_id". So, if you have a column with ocid's in your import file, title it "oc_id" and map it to "User Account Number" to dedupe against ocid.**//
--//For example~:// You wish to change an assigned code (e.g. a class or subscription type code) for a group of users subscribed to a particular product. First, you would export the list (for more on how to generate lists see the LISTS AND REPORTS Manual), then do a "find and replace" for the code in the exported csv file, and then reimport the file with the new code. The Bulk Operations feature allows you to make bulk status changes, product changes, unsubscribes/ kills, subscriptions to additional products, and to delete multiple records without having to reimport a list. It does not allow for bulk demographic changes at this time. More information can be found in the [[BULK OPERATIONS >>doc:Import and Bulk Operations Essentials (v12\.x)]]section of the USER OPERATIONS Manual.
++//For example~:// You wish to change an assigned code (e.g. a class or subscription type code) for a group of users subscribed to a particular product. First, you would export the list (for more on how to generate lists see the LISTS AND REPORTS Manual), then do a "find and replace" for the code in the exported csv file, and then reimport the file with the new code. The Bulk Operations feature allows you to make bulk status changes, product changes, unsubscribes/ kills, subscriptions to additional products, and to delete multiple records without having to reimport a list. It does not allow for bulk demographic changes at this time. More informaiton can be found in the BULK OPERATIONS section of the USER OPERATIONS Manual.
--
++=== 6. Select from the Request Date drop-down menu the field/column from your import file to map as the Request Date. (If you don't map this field, the Request Date will be the same as the Transaction Date, which is the date of the import.) ===
--**6. Select from the Request Date drop-down menu the field/column from your import file to map as the Request Date. (If you don't map this field, the Request Date will be the same as the Transaction Date, which is the date of the import.)**
--
  [[image:attach:6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png||align="center"]]
--{{tip}}
  Setting a request date ensures that when processing duplicates only data in the ONEcount database that is older than data in the import file will be written over. ONEcount will compare the request date to the date of the most recent information in the database and only write over information that is older than the request date. //This is done on a field-by-field basis within a record.//
--{{/tip}}
  **For example**:
--(% style="margin-left: 30.0px;" %)
  A list is being imported on 01/07/2013, and an import record is identified as a duplicate.
--(% style="margin-left: 30.0px;" %)
  The mapped request date of the import record is 12/01/2012, and the user's last name in the import file is Smith.
--(% style="margin-left: 30.0px;" %)
  The user updated her profile in the ONEcount database by changing her last name from Smith to Jones on 12/31/2012.
--*
--** When duplicates are processed, her last name WILL NOT be written over, as she changed it AFTER (12/31/2012) the request date of the import record (12/01/2012).
++* When duplicates are processed, her last name WILL NOT be written over, as she changed it AFTER (12/31/2012) the request date of the import record (12/01/2012).
--(% style="margin-left: 30.0px;" %)
  As of 11/25/2012 her job title in the ONEcount database is "Sales Associate".
--(% style="margin-left: 30.0px;" %)
  In the import record (Request Date 12/01/2012), her job title is "Regional Sales Manager".
--(% style="margin-left: 30.0px;" %)
  When duplicates are processed, her job title WILL be written over, as the data as of the request date (12/01/2012) is more recent than the data in the ONEcount database (11/25/20120.
--(% style="margin-left: 30.0px;" %)
  If no request date is set when importing, the request date will be the date of the import. If this were the case in the example above, both the user's last name and job title would be written over as the request date (01/07/2013, which is the date of the import/transaction) would be more recent than the dates in the ONEcount database.
--(% style="margin-left: 30.0px;" %)
  If there is a blank field in an import file and the corresponding field in the ONEcount database contains data, that field in the ONEcount database will NOT be written over with a blank, even if the Request Date of the import is more recent than the date the information was entered into the ONEcount database.
--(% style="margin-left: 30.0px;" %)
  If "Null" is inserted into a field in the import file and the corresponding field in the ONEcount database contains data, that field in the ONEcount database WILL BE written over with a blank if the request date of the import is more recent than the date the information was entered into the ONEcount database. If the request date is older than the date the information was entered in the database, the corresponding field will NOT be written over with a blank.
--(% style="margin-left: 30.0px;" %)
--
++=== 7. Select the column/field in your import file to specify the product Expiration Date. (If you don't specify this, the product Expiration Date will be based upon the Transaction Date, which is the date of the import.) ===
--**7. Select the column/field in your import file to specify the product Expiration Date. (If you don't specify this, the product Expiration Date will be based upon the Transaction Date, which is the date of the import.)**
--
  [[image:attach:7.__Select_the_columnfield_in_your_import_file_to_specify.png||align="center"]]
  The expiration date is automatically calculated when a user subscribes online based on the transaction date (which is the date of the online subscription). If a subscription transaction with an expiration date is recorded in the system via an import – especially for data conversions when implementing a new ONEcount system – "Expiration Date" (or something similar) should be a field in the CSV import file. If you do not select this field to be recorded as the expiration date in the ONEcount system, the system will set the expiration date based on the transaction date (which isn't an issue for new subscribers being imported into the system.)
--(% style="margin-left: 30.0px;" %)
  **For example:**
   A product has a term of three years.
  If a user subscribes online, their subscription will expire three yeasr from the date of their submittal of the subscription form.
  If, however – as in the case of an initial data conversion when implementing a new ONEcount system – lists of users who didn't subscribe to the products online via the ONEcount system are being imported, the import files should contain a field with the expiration date based on the actual subscription date, and that field should be selected as the expiration date. Otherwise, the system will look at the date of import (transaction date) and set the expiration date as three-years from then.
--
++(% style="color: rgb(255,0,0);" %)**Note that if you select Expiration Date and select multiple products when importing, the value of that field for each row of the import file will be used to update the Expiration Date for //all// of the products selected.**
--{{error}}
--Note that if you select Expiration Date and select multiple products when importing, the value of that field for each row of the import file will be used to update the Expiration Date for //all// of the products selected.
--{{/error}}
--
--**
--**
--
--
--
--(% style="margin-left: 30.0px;" %)
  If data for a user already in the ONEcount system is being re-imported (e.g., to append information to his/her ONEcount profile) and:
--
--(% style="margin-left: 30.0px;" %)
--
--1) the user is imported to a product he/she is already subscribed to, and
++ 1) the user is imported to a product he/she is already subscribed to, and
 ) Expiration Date is specified
--\\ The transaction will show as a renewal to the product and the earlier of the two expiration dates will be ignored. That is, if the expiration date specified in the import file is earlier than the expiration date already in ONEcount, the transaction will appear as a product renewal and the expiration date in ONEcount will not be changed. So, for example, if a user is already subscribed to "Print Magazine" product and the expiration date in ONEcount is 01-01-2015 and that same user is re-imported to that same product with an expiration date in the import file of 01-01-2014, the 01-01-2014 date will be ignored.
++ The transaction will show as a renewal to the product and the earlier of the two expiration dates will be ignored. That is, if the expiration date specified in the import file is earlier than the expiration date already in ONEcount, the transaction will appear as a product renewal and the expiration date in ONEcount will not be changed. So, for example, if a user is already subscribed to "Print Magazine" product and the expiration date in ONEcount is 01-01-2015 and that same user is re-imported to that same product with an expiration date in the import file of 01-01-2014, the 01-01-2014 date will be ignored.
--(% style="margin-left: 30.0px;" %)
--
++=== 8. To link media files for a record to the folder on your server where the media files are stored, select the column/field from your import file and the folder on your server where media files are stored.* ===
--**8. To link media files for a record to the folder on your server where the media files are stored, select the column/field from your import file and the folder on your server where media files are stored.***
--
  [[image:attach:8.__To_link_media_files_for_a_record_to_the_folder_on_you.png||align="center"]]
  *This server must be connected to ONEcount.
@@ -213,18 +213,14 @@
  To link to a file stored on your server, e.g. scanned subscription/renewal cards, enter the path to the file in a column in your import file. Then select the folder on your server where the files are stored. This information will need to be provided to ONEcount so that it can be configured in the ONEcount back end and the folder selections displayed here.
--
++=== 9. Click the "Set" button. ===
--**9. Click the "Set" button.**
--
  [[image:attach:media_1443551680910.png||align="center"]]
  You can now either Save the Mapping (See "How to Create an Import Mapping Template" lesson), Import the file, or Reset the mapping.
--
++=== 10. Click on the Import button. ===
--**10. Click on the Import button.**
--
  [[image:attach:media_1443551721550.png||align="center"]]
  The system will begin to process the import, and a Pre-Import Summary and Sample Mapping page will appear. (See screen shots and important information below.)
@@ -233,10 +233,8 @@
  Clicking on "Save Mapping Template" will save the mappings to a template. See Mapping Template documentation for more detail.
--
++=== 11. Review the Pre-Import Summary ===
--**~11. Review the Pre-Import Summary**
--
  [[image:attach:11.__Review_the_Pre-Import_Summary.png||align="center"]]
  The system will alert you if there are records in your import file that match records in the ONEcount database based on the field(s) you select to check for duplicates. The pre-import summary screen will give you the number of new records to be imported (1), the number of duplicates (if any) in the import file (2), and the number of duplicates matched in the database (3).
@@ -245,242 +245,86 @@
  The number of "Duplicate Records Matched in Database" is the number of records within the database that match the field(s) you selected to check for duplicates.
--{{error}}
--(% style="color: rgb(0,51,102);" %)**The number of duplicates in the file and matched in the database should be the same. If there is a difference in the numbers, it's recommended NOT to process the duplicates but instead to go back and select an additional field(s) to check for duplicates or import the new records and download the duplicates for review prior to processing. (See example and screenshot below.)**
--{{/error}}
++(% style="color: rgb(255,0,0);" %)The number of duplicates in the file and matched in the database should be the same. If there is a difference in the numbers, it's recommended NOT to process the duplicates but instead to go back and select an additional field(s) to check for duplicates or import the new records and download the duplicates for review prior to processing. (See example and screenshot below.)
  (% style="color: rgb(0,0,0);" %)//**EXAMPLE**//(% style="color: rgb(196,0,0);" %):
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)You check for duplicates across email.
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)The import file contains one record with a blank email field and three records that are already in the ONEcount database.
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)There are six records with blank email fields in the ONEcount database.
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)ONEcount will identify the one record in the import file and the six recordsin ONEcount as duplicates (because they all have a blank email, which matches the record being imported).
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)The system will also identify the three records in the import file that already exist in the ONEcount database as duplicates.
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)The pre-import summary would say:
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)Duplicate records in file = 4 (the 1 with the blank email and the 3 already in the ONEcount database), and
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)Duplicate records matched in the database = 9 (the 6 records with blank emails in the ONEcount database plus the 3 records that are already in the ONEcount database). See screenshot below.
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)If you check across at least one other field, say **last name**, a record in the upload file and a record in the ONEcount database – each with an empty email field but with a last name – will not be considered duplicates unless they have an empty email field AND the same last name.
  [[image:attach:media_1366813790837.png||align="center"]]
--
++=== 12. Review the Sample Mapping ===
--**12. Review the Sample Mapping**
--
  [[image:attach:12.__Review_the_Sample_Mapping.png||align="center"]]
  Sample Mapping gives you a preview of the data import. Five records will be displayed, each including the data from the import file and the field within ONEcount that it will be imported to. In the example above, the email address "spongy@bob.com" will be imported into the Email Address field in the ONEcount database, the first name "spongebob" will be imported into the First Name field in the ONEcout database, and the last name "squarepants" will be imported into the Last Name field in the ONEcount database. No data is shown in the "State Licensed" field, indicating that that field in the import file was empty.
--(% style="color: rgb(230,0,0);" %)** **
++(% style="color: rgb(230,0,0);" %)**If a record(s) has a blank field in an import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in ONEcount will NOT be written over with a blank, even if the Request Date of the import is more recent than the date the information was entered into the ONEcount database.**
--{{tip}}
--(% style="color: rgb(0,51,102);" %)**If a record(s) has a blank field in an import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in ONEcount will NOT be written over with a blank, even if the Request Date of the import is more recent than the date the information was entered into the ONEcount database.**
++(% style="color: rgb(255,0,0);" %)**If a record has "Null" in a field in the import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in the ONEcount database WILL BE written over with a blank if the request date of the import is more recent than the date the informaton was entered into the ONEcount database. If the request date is older than the date the information was entered in the database, the corresponding field will NOT be written over with a blank.**
--(% style="color: rgb(255,0,0);" %)** **
--{{/tip}}
++=== 13. If everything looks good in the Sample Mapping, click the "Proceed" button at the bottom of the page. ===
--(% style="color: rgb(255,0,0);" %)** **
--
--{{tip}}
--**If a record has "Null" in a field in the import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in the ONEcount database WILL BE written over with a blank if the request date of the import is more recent than the date the informaton was entered into the ONEcount database. If the request date is older than the date the information was entered in the database, the corresponding field will NOT be written over with a blank.**
--
--(% style="color: rgb(255,0,0);" %)** **
--{{/tip}}
--
--(% style="color: rgb(255,0,0);" %)**
--**
--
--**13. If everything looks good in the Sample Mapping, click the "Proceed" button at the bottom of the page.**
--
  [[image:attach:media_1443552112267.png||align="center"]]
  All new records will be imported into ONEcount, and a post-import summary will be displayed.
--
++=== 14. Review the Post-Import Summary and Download Lists of Duplicates and/or Process Duplicates. (See important information below.) ===
--**14. Review the Post-Import Summary and Download Lists of Duplicates and/or Process Duplicates. (See important information below.)**
--
  [[image:attach:media_1443552145622.png||align="center"]]
  The screenshot above shows a post-import summary without any duplicates, so at this point the import is complete.
--The screenshot below shows a post-import summary with duplicates, and the total matched duplicates in the database and the total duplicates in the file don't match. At this point, you have the option to either Download Duplicates in the File, Download Duplicates in ONEcount, or Process Duplicates.
++The screenshot below shows a post-import summary with duplicates, and the total matched duplicates in the database and the total duplicates in the file don't match. At this point, you have the option to either Download Duplicates in the File, Downlod Duplicates in ONEcount, or Process Duplicates.
--
++=== a. "Download Duplicates in file" and "Download Duplicates in ONEcount" ===
--(% style="margin-left: 30.0px;" %)
--**a. "__Download Duplicates in file" and "Download Duplicates in ONEcount"__**
--
--(% style="margin-left: 60.0px;" %)
  [[image:attach:media_1443552610096.png||align="center"]]
--(% style="margin-left: 60.0px;" %)
  (% style="color: rgb(0,0,0);" %)**Download Duplicates in file** will create a .csv file of all the records in the import file that have been identified as duplicates of records in the ONEcount database, based on the field(s) you selected to check duplicates.
--(% style="margin-left: 60.0px;" %)
  (% style="color: rgb(0,0,0);" %)**Download Duplicates in ONEount** will create a .csv file of all the records in ONEcount that have been identified as duplicates of records in the import file, based on the field(s) you selected to check duplicates.
--(% style="margin-left: 60.0px;" %)
++(% style="color: rgb(0,0,0);" %)**Process Duplicates **will update the records in the ONEcount database identified as duplicates of records in the import file.
++
  (% style="color: rgb(0,0,0);" %)You can download duplicates both in the file and in ONEcount and review. This window will remain open, so after review you can either process the duplicates or quit if you don't want to process at that time. (%%)
  (% style="color: rgb(0,0,0);" %)Note that if you leave the window open for too long, you'll be logged out of ONEcount and will need to log back in to continue.
--(% style="margin-left: 60.0px;" %)
  (% style="color: rgb(0,0,0);" %)**Using the Example from Step 11 above:**(%%)
-- (% style="color: rgb(0,0,0);" %)"Download Duplicates in ONEcount" will create a .csv file of the 9 records in ONEcount that are identified as duplicates of records in the import file.
--\\Using the example in Step 11 above, **6** of the duplicates will have a blank email field (which matches the one record in the import file without an email) and **3** will be records that match the email addresses of 3 records in the import file.
++ (% style="color: rgb(0,0,0);" %)"Download Duplicates in ONEcount" will create a .csv file of the 9 records in ONEcount that are identified as duplicates of records in the import file. Using the example in Step 11 above, **6** of the duplicates will have a blank email field (which matches the one record in the import file without an email) and **3** will be records that match the email addresses of 3 records in the import file.
--(% style="margin-left: 60.0px;" %)
  "Download Duplicates in the file" will create a .csv file of the 4 records in the import file that are already in the ONEcount database: (% style="color: rgb(0,0,0);" %)the **1** record with the blank email (whicht matches the 6 records with blank email field in ONEcount) and the 3 that match the email addresses of **3** records already in the ONEcount database.
--(% style="margin-left: 60.0px;" %)
--(% style="color: rgb(0,0,0);" %)T(%%)he import window will remain open so you can process the duplicates after reviewing the list if you choose to do so.\\
++(% style="color: rgb(0,0,0);" %)T(%%)he import window will remain open so you can process the duplicates after reviewing the list if you choose to do so. (% style="color: rgb(255,0,0);" %)**It is recommended to review the list of duplicates both in the file and ine ONEcount prior to processing them in a situation where the numbers of Total Matched Duplicates in the Database and the Total Duplicates in the File don't match.**
--
++(% style="color: rgb(255,0,0);" %)If you didn't set a Request Date or the Request Date you selected is newer than the information in the ONEcount database and then you opt to "Process Duplicates", all of the mapped fields for the six records with a blank email field in the ONEcount database will be written over with the information from the ONE record with the blank email field in the upload file, AND the three records identified by email as already being in the ONEcount database will be written over with the corresponding data for those records in the import file.
--{{error}}
--It is recommended to review the list of duplicates both in the file and in ONEcount prior to processing them in a situation where the numbers of Total Matched Duplicates in the Database and the Total Duplicates in the File don't match.
--{{/error}}
++(% style="color: rgb(0,0,0);" %)//If processing duplicates, selecting a request date on import ensures that only data in the ONEcount database that is older than data in the import file will be written over. ONEcount will compare the request date to the date of the most recent information in the database and only write over information that is older than the request date. This is done on a field-by-field basis within a record.//
--{{error}}
--If you didn't set a Request Date or the Request Date you selected is newer than the information in the ONEcount database and then you opt to "Process Duplicates", all of the mapped fields for the six records with a blank email field in the ONEcount database will be written over with the information from the ONE record with the blank email field in the upload file, AND the three records identified by email as already being in the ONEcount database will be written over with the corresponding data for those records in the import file.
--{{/error}}
--
--{{tip}}
--If processing duplicates, selecting a request date on import ensures that only data in the ONEcount database that is older than data in the import file will be written over. ONEcount will compare the request date to the date of the most recent information in the database and only write over information that is older than the request date. This is done on a field-by-field basis within a record.
--{{/tip}}
--
--
--
--(% style="margin-left: 30.0px;" %)
  (% style="color: rgb(0,0,0);" %)If there are, say, three records with a blank email field in the import file, then the mapped fields for the six records with a blank email field in the ONEcount database will be written over with the information from the last record with a blank email field in the import file.
--(% style="margin-left: 30.0px;" %)
--(% style="color: rgb(0,0,0);" %)
++=== b. Process Duplicates ===
--
--(% style="margin-left: 30.0px;" %)
--
--
--(% style="margin-left: 30.0px;" %)
--**b. __Process Duplicates__**
--
--(% style="margin-left: 30.0px;" %)
--(% style="color: rgb(0,0,0);" %)**Process Duplicates **will update the records in the ONEcount database identified as duplicates of records in the import file.
--
--(% style="margin-left: 30.0px;" %)
  If you process duplicates, either with or without downloading and reviewing duplicates, the message below will appear when finished processing. At this point, your import is complete.
--(% style="margin-left: 30.0px;" %)
  [[image:attach:media_1443556620318.png||align="center"]]
  {{id name="End ScreenSteps Content"/}}
--{{/layout-cell}}
--
--{{layout-cell}}
--{{panel title="Search All Documentation:"}}
--
--
--{{livesearch/}}
--{{/panel}}
--
--{{panel title="Search USER OPERATIONS Documentation:"}}
--
--
--{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
--{{/panel}}
--
--{{panel title="On this page:"}}
--
--
--{{toc/}}
--{{/panel}}
--
--{{panel title="More USER OPERATIONS Documentation"}}
--{{expand}}
-- **Add Users
--**
--
--(% style="margin-left: 60.0px;" %)
--
--
--(% style="margin-left: 60.0px;" %)
--[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Pre-Import Checklist>>doc:Pre-Import Checklist (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--
--
--(% style="margin-left: 60.0px;" %)
--[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Add Audience>>doc:Add Audience (v12\.x)]]
--
--(% style="margin-left: 30.0px;" %)
--**Batch Operations**
--
--(% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Delete>>doc:Bulk Operation - How to Perform a Batch Delete (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Product Change>>doc:Bulk Operation - How to Perform a Batch Product Change (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Status Change>>doc:Bulk Operation - How to Perform a Batch Status Change (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation  - How to Perform a Batch UnsubscribeKill (v12\.x)]]
--
--(% style="margin-left: 60.0px;" %)
--[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users (v12\.x)]]
--
--(% style="margin-left: 30.0px;" %)
--**Target Audience Segments**
--
--(% style="margin-left: 60.0px;" %)
--(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc:Utilities - Target Engine  (v12\.x)]]__
--__
--
--
--
--
--{{/expand}}
--{{/panel}}
--
--
--
--
--
--
--
--
--{{/layout-cell}}
--{{/layout-section}}
--{{/layout}}

Confluence.Code.ConfluencePageClass[0]

id

@@ -1,1 +1,1 @@
--67535
++66920

url

@@ -1,1 +1,1 @@
--https://info.onecount.net//wiki/spaces/OD/pages/67535/Import - How to Import a File (v12.x)
++https://info.onecount.net//wiki/spaces/OD/pages/66920/Import - How to Import a File (v12.x)