Last modified by caterina on 2021/10/27 16:31
From version 7.1
edited by melanie@one-count_com
on 2016/12/14 14:50
Change comment: There is no comment for this version
To version 5.1
edited by melanie@one-count_com
on 2016/12/14 14:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,8 +26,6 @@
26 26  
27 27  === IMPORT STEPS ===
28 28  
29 -==== Select Import File ====
30 -
31 31  **~1. In the Import window choose your import file using the "Browse" button (1), and select "Upload File" (2).**
32 32  
33 33  [[image:attach:media_1443213396710.png||align="center"]]
... ... @@ -38,8 +38,6 @@
38 38  
39 39  
40 40  
41 -==== Complete Import Information ====
42 -
43 43  **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.**
44 44  
45 45  [[image:attach:media_1443549296560.png||align="center"]]
... ... @@ -60,8 +60,6 @@
60 60  
61 61  
62 62  
63 -==== Map Data ====
64 -
65 65  **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.**
66 66  
67 67  [[image:attach:media_1362667166234.png||align="center"]]
... ... @@ -117,35 +117,18 @@
117 117  
118 118  You can select multiple headers to check for duplicates, but be aware that ONEcount uses “AND” logic when doing so. (% style="color: rgb(0,0,0);" %)For example, if you select to check email, first name, and last name fields for duplicates, ONEcount will look for records in the ONEcount database that have the same email AND first name AND last name as a record being imported. A record would be a duplicate only if all three fields match.
119 119  
120 -
114 +(% style="color: rgb(255,0,0);" %)**When checking for duplicates, ONEcount is not checking for duplicates within the import file but only between the ONEcount database and the file being imported. If your import file contains duplicates within it and no matching records are found in ONEcount, the duplicate records in the import file will be imported.**
121 121  
122 -{{error}}
123 -It is important to be sure that records in ONEcount and the import file contain data for the fields you are checking for duplicates against. If they don't, a record may not be matched as a duplicate. For example, you check for duplicates against email AND last name: a record in ONEcount has the same email as a record in the import file and the ONEcount record DOES include last name. The record in the import file DOESN'T include last name. The record won't be counted as a duplicate because the email AND last name do not match.
124 -{{/error}}
116 +(% style="color: rgb(255,0,0);" %)**It is important to be sure that records in ONEcount and the import file contain data for the fields you are checking for duplicates against. If they don't, a record may not be matched as a duplicate. For example, you check for duplicates against email AND last name: a record in ONEcount has the same email as a record in the import file and the ONEcount record DOES include last name. The record in the import file DOESN'T include last name. The record won't be counted as a duplicate because the email AND last name do not match.**
125 125  
126 -**
127 -**
128 -
129 -{{tip}}
130 -When checking for duplicates, ONEcount is not checking for duplicates within the import file but only between the ONEcount database and the file being imported. If your import file contains duplicates within it and no matching records are found in ONEcount, the duplicate records in the import file will be imported.
131 -{{/tip}}
132 -
133 -{{tip}}
134 134  If importing a new list and email is a required field for all records (e.g. for an e-newsletter-type product), it is recommended to check for duplicates across ***email**.* _ (% style="color: rgb(255,0,0);" %)**Note that if a user has a different email in the import list than in ONEcount and you check only by email, the record won't be identified as a duplicate**(%%)_(% style="color: rgb(255,0,0);" %). (%%)If the emails match (and the records identified as duplicates) and you wish to append data to that record and/or subscribe to a new product via the import file, you will need to select to process duplicates after new records are imported. This will process ALL duplicates.
135 -{{/tip}}
136 136  
137 -{{tip}}
138 -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.**//
120 +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.**//
139 139  
140 -//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]]section of the USER OPERATIONS Manual.
122 +//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.
141 141  
142 142  
143 -{{/tip}}
144 144  
145 -
146 -
147 -==== Request Date | Expiration Date | Link to Media Files ====
148 -
149 149  **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.)**
150 150  
151 151  [[image:attach:6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png||align="center"]]
... ... @@ -238,8 +238,6 @@
238 238  
239 239  
240 240  
241 -==== Set and Import ====
242 -
243 243  **9. Click the "Set" button.**
244 244  
245 245  [[image:attach:media_1443551680910.png||align="center"]]
... ... @@ -260,8 +260,6 @@
260 260  
261 261  
262 262  
263 -==== Pre-Import Summary and Sample Mapping ====
264 -
265 265  **~11. Review the Pre-Import Summary**
266 266  
267 267  [[image:attach:11.__Review_the_Pre-Import_Summary.png||align="center"]]
... ... @@ -268,13 +268,9 @@
268 268  
269 269  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).
270 270  
271 -{{tip}}
272 272  The number of "Duplicate Records in File" is how many records within the import file are already in the ONEcount database based on your selected field(s) to check for duplicates. **THIS IS NOT A COUNT OF THE NUMBER OF RECORDS //WITHIN// THE IMPORT FILE THAT ARE DUPLICATES.**
273 -{{/tip}}
274 274  
275 -{{tip}}
276 276  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.
277 -{{/tip}}
278 278  
279 279  {{error}}
280 280  (% 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.)**
... ... @@ -344,7 +344,7 @@
344 344  
345 345  All new records will be imported into ONEcount, and a post-import summary will be displayed.
346 346  
347 -==== Post-Import Summary ====
316 +
348 348  
349 349  **14. Review the Post-Import Summary and Download Lists of Duplicates and/or Process Duplicates. (See important information below.)**
350 350  
... ... @@ -381,7 +381,7 @@
381 381  "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.
382 382  
383 383  (% style="margin-left: 60.0px;" %)
384 -(% 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.
353 +(% 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.\\
385 385  
386 386  
387 387  
... ... @@ -454,10 +454,10 @@
454 454  
455 455  
456 456  (% style="margin-left: 60.0px;" %)
457 -[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import]]
426 +[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import (v12\.x)]]
458 458  
459 459  (% style="margin-left: 60.0px;" %)
460 -[[Pre-Import Checklist>>doc:Pre-Import Checklist]]
429 +[[Pre-Import Checklist>>doc:Pre-Import Checklist (v12\.x)]]
461 461  
462 462  (% style="margin-left: 60.0px;" %)
463 463  
... ... @@ -496,7 +496,7 @@
496 496  **Target Audience Segments**
497 497  
498 498  (% style="margin-left: 60.0px;" %)
499 -(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc:Utilities - Target Engine]]__
468 +(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc:Utilities - Target Engine (v12\.x)]]__
500 500  __
501 501  
502 502  
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -11927730
1 +67535
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/11927730/Import - How to Import a File (v12.x)
1 +https://info.onecount.net//wiki/spaces/OD/pages/67535/Import - How to Import a File (v12.x)