Changes for page Import - How to Import a File
Last modified by caterina on 2021/10/27 16:31
Summary
-
Page properties (4 modified, 0 added, 0 removed)
-
Attachments (0 modified, 24 added, 0 removed)
- 11.__Review_the_Pre-Import_Summary.png
- 12.__Review_the_Sample_Mapping.png
- 3b.__If_not_using_an_Import_Mapping_Template__The_mapping.png
- 4._Proceed_to_the_mapping_section_and_map_your_fields___1.png
- 5.__DO_NOT_SKIP_THIS_STEP_--_ALWAYS_CHECK_FOR_DUPLICATES_.png
- 6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png
- 7.__Select_the_columnfield_in_your_import_file_to_specify.png
- 8.__To_link_media_files_for_a_record_to_the_folder_on_you.png
- Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 3.png
- Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 4.png
- media_1362667166234.png
- media_1366813790837.png
- media_1406494045151.png
- media_1443213231223.png
- media_1443213261172.png
- media_1443213294962.png
- media_1443213396710.png
- media_1443549296560.png
- media_1443551680910.png
- media_1443551721550.png
- media_1443552112267.png
- media_1443552145622.png
- media_1443552610096.png
- media_1443556620318.png
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Import - How to Import a File (v12.x)1 +Import - How to Import a File - Parent
-
... ... @@ -1,0 +1,1 @@ 1 +User Operations - Managing Your Data - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. melanie@one-count_com1 +XWiki.caterina - Content
-
... ... @@ -4,7 +4,7 @@ 4 4 5 5 6 6 {{id name="Start ScreenSteps Content"/}} 7 - 7 +This lesson will describe how to use the Import Engine to upload a CSV formatted list of users into the ONEcount database. 8 8 9 9 Please refer to Quick Start Guide - User Operations for important information about basic concepts and rules relating to imports and bulk operations. 10 10 ... ... @@ -12,13 +12,13 @@ 12 12 13 13 **Select USER OPERATIONS from the Main Menu.** 14 14 15 -[[image:attach: media_1443213231223.png||align="center"]]15 +[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 3.png||thumbnail="true" height="250"]] 16 16 17 17 **Click on "IMPORT" in the sub-menu.** 18 18 19 - [[image:attach:media_1443213261172.png||align="center"]]19 +\\ 20 20 21 - 21 +[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 4.png||thumbnail="true" height="250"]] 22 22 23 23 **The "Import" window will open, where you begin begin the import process.** 24 24 ... ... @@ -26,6 +26,8 @@ 26 26 27 27 === IMPORT STEPS === 28 28 29 +==== Select Import File ==== 30 + 29 29 **~1. In the Import window choose your import file using the "Browse" button (1), and select "Upload File" (2).** 30 30 31 31 [[image:attach:media_1443213396710.png||align="center"]] ... ... @@ -34,8 +34,10 @@ 34 34 35 35 [[image:attach:media_1406494045151.png||align="center"]] 36 36 37 - 39 +\\ 38 38 41 +==== Complete Import Information ==== 42 + 39 39 **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.** 40 40 41 41 [[image:attach:media_1443549296560.png||align="center"]] ... ... @@ -45,7 +45,7 @@ 45 45 **Source Codes** are used to track the source of a transaction, ie the source of the user/name in the ONEcount database.* When assigned to a form, a source code can be used as a selection when generating lists and reports, to track what form a user/subscriber completed, to track what list a user came from when importing users, or to show which e-mail campaign a user came from . (A source code tag can be appended to links in a newsletter campaign to override a source code assigned when a form is created, which allows you to identify that a user was directed to a form and came into the system from a link in that campaign.) Source Codes are created using the Source Codes tool in the INVENTORY module. 46 46 47 47 *For audited publications, source codes that identify the source of user names in accordance with cagetories in Paragraph 3b reports should be created. Forms and imported lists should be assigned the appropriate source code for the source of the name. For example: 48 - 52 +1) You want to identify all Internet Direct Requests from a subscription form, so you would create a source code called, for example, IDRPrintForm and attach it to the subscription form. This source code will be attached to any user record created when a user subscribes using that form. The source codes indicates it was an Internet Direct Request from the form, and when a 3b report is generated those users will be included in the count for internet direct requests. 49 49 2) You want to identify all Telecommunications Direct Requests from a telemarketing renewal campaign, so you create source code called, for example, TDR05152104 to identify that renewal list imported on May 15, 2014. When doing the import to update/renew, select that source code and all records imported will have that source attached to their record in ONEcount. So, when generating a 3b report those renewed users will be included in the count for telecommunications direct requests. 50 50 51 51 If you have a master file including multiple codes for circulationc sources, separate the file by source (e.g. a sub-file for each 3b category/source of circulation) and import each sub-file using the appropriate source code created in ONEcount. ... ... @@ -54,8 +54,10 @@ 54 54 55 55 Below the Product List, you will see a list of any existing Import Mappings (templates), if any. 56 56 57 - 61 +\\ 58 58 63 +==== Map Data ==== 64 + 59 59 **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.** 60 60 61 61 [[image:attach:media_1362667166234.png||align="center"]] ... ... @@ -64,13 +64,13 @@ 64 64 65 65 You may select to use a template and then modify it by adding/removing fields to be mapped (as described in Step 4.) 66 66 67 - 73 +\\ 68 68 69 69 **3b. If not using an Import Mapping Template: The mapping function is found below the list of mapping templates. Proceed to Step 4.** 70 70 71 71 [[image:attach:3b.__If_not_using_an_Import_Mapping_Template__The_mapping.png||align="center"]] 72 72 73 - 79 +\\ 74 74 75 75 **4. Proceed to the mapping section and map your fields (either from scratch or by modifying an Import Mapping Template).** 76 76 ... ... @@ -99,7 +99,7 @@ 99 99 100 100 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". 101 101 102 - 108 +\\ 103 103 104 104 {{error}} 105 105 **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.** ... ... @@ -111,18 +111,35 @@ 111 111 112 112 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. 113 113 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.**120 +\\ 115 115 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.** 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}} 117 117 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}} 118 118 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}} 119 119 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.**// 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.**// 121 121 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.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. 123 123 124 - 142 +\\ 143 +{{/tip}} 125 125 145 +\\ 146 + 147 +==== Request Date | Expiration Date | Link to Media Files ==== 148 + 126 126 **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.)** 127 127 128 128 [[image:attach:6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png||align="center"]] ... ... @@ -164,7 +164,7 @@ 164 164 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. 165 165 166 166 (% style="margin-left: 30.0px;" %) 167 - 190 +\\ 168 168 169 169 **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.)** 170 170 ... ... @@ -174,11 +174,11 @@ 174 174 175 175 (% style="margin-left: 30.0px;" %) 176 176 **For example:** 177 - 200 +A product has a term of three years. 178 178 If a user subscribes online, their subscription will expire three yeasr from the date of their submittal of the subscription form. 179 179 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. 180 180 181 - 204 +\\ 182 182 183 183 {{error}} 184 184 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. ... ... @@ -187,7 +187,7 @@ 187 187 ** 188 188 ** 189 189 190 - 213 +\\ 191 191 192 192 (% style="margin-left: 30.0px;" %) 193 193 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: ... ... @@ -196,10 +196,10 @@ 196 196 197 197 1) the user is imported to a product he/she is already subscribed to, and 198 198 2) Expiration Date is specified 199 -\\ 222 +\\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. 200 200 201 201 (% style="margin-left: 30.0px;" %) 202 - 225 +\\ 203 203 204 204 **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.*** 205 205 ... ... @@ -213,8 +213,10 @@ 213 213 214 214 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. 215 215 216 - 239 +\\ 217 217 241 +==== Set and Import ==== 242 + 218 218 **9. Click the "Set" button.** 219 219 220 220 [[image:attach:media_1443551680910.png||align="center"]] ... ... @@ -221,7 +221,7 @@ 221 221 222 222 You can now either Save the Mapping (See "How to Create an Import Mapping Template" lesson), Import the file, or Reset the mapping. 223 223 224 - 249 +\\ 225 225 226 226 **10. Click on the Import button.** 227 227 ... ... @@ -233,8 +233,10 @@ 233 233 234 234 Clicking on "Save Mapping Template" will save the mappings to a template. See Mapping Template documentation for more detail. 235 235 236 - 261 +\\ 237 237 263 +==== Pre-Import Summary and Sample Mapping ==== 264 + 238 238 **~11. Review the Pre-Import Summary** 239 239 240 240 [[image:attach:11.__Review_the_Pre-Import_Summary.png||align="center"]] ... ... @@ -241,9 +241,13 @@ 241 241 242 242 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). 243 243 271 +{{tip}} 244 244 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}} 245 245 275 +{{tip}} 246 246 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}} 247 247 248 248 {{error}} 249 249 (% 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.)** ... ... @@ -280,7 +280,7 @@ 280 280 281 281 [[image:attach:media_1366813790837.png||align="center"]] 282 282 283 - 314 +\\ 284 284 285 285 **12. Review the Sample Mapping** 286 286 ... ... @@ -313,7 +313,7 @@ 313 313 314 314 All new records will be imported into ONEcount, and a post-import summary will be displayed. 315 315 316 - 347 +==== Post-Import Summary ==== 317 317 318 318 **14. Review the Post-Import Summary and Download Lists of Duplicates and/or Process Duplicates. (See important information below.)** 319 319 ... ... @@ -323,7 +323,7 @@ 323 323 324 324 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. 325 325 326 - 357 +\\ 327 327 328 328 (% style="margin-left: 30.0px;" %) 329 329 **a. "__Download Duplicates in file" and "Download Duplicates in ONEcount"__** ... ... @@ -343,7 +343,7 @@ 343 343 344 344 (% style="margin-left: 60.0px;" %) 345 345 (% style="color: rgb(0,0,0);" %)**Using the Example from Step 11 above:**(%%) 346 - 377 +(% 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. 347 347 \\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. 348 348 349 349 (% style="margin-left: 60.0px;" %) ... ... @@ -350,9 +350,9 @@ 350 350 "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. 351 351 352 352 (% style="margin-left: 60.0px;" %) 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. \\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. 354 354 355 - 386 +\\ 356 356 357 357 {{error}} 358 358 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. ... ... @@ -366,7 +366,7 @@ 366 366 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. 367 367 {{/tip}} 368 368 369 - 400 +\\ 370 370 371 371 (% style="margin-left: 30.0px;" %) 372 372 (% 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. ... ... @@ -376,7 +376,7 @@ 376 376 377 377 378 378 (% style="margin-left: 30.0px;" %) 379 - 410 +\\ 380 380 381 381 (% style="margin-left: 30.0px;" %) 382 382 **b. __Process Duplicates__** ... ... @@ -423,64 +423,64 @@ 423 423 424 424 425 425 (% style="margin-left: 60.0px;" %) 426 -[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import (v12\.x)]]457 +[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import]] 427 427 428 428 (% style="margin-left: 60.0px;" %) 429 -[[ Pre-Import Checklist>>doc:Pre-Import Checklist(v12\.x)]]460 +[[doc:Pre-Import Checklist]] 430 430 431 431 (% style="margin-left: 60.0px;" %) 432 432 433 433 434 434 (% style="margin-left: 60.0px;" %) 435 -[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template (v12\.x)]]466 +[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template]] 436 436 437 437 (% style="margin-left: 60.0px;" %) 438 -[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template (v12\.x)]]469 +[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template]] 439 439 440 440 (% style="margin-left: 60.0px;" %) 441 -[[ Add Audience>>doc:Add Audience(v12\.x)]]472 +[[doc:Add Audience]] 442 442 443 443 (% style="margin-left: 30.0px;" %) 444 444 **Batch Operations** 445 445 446 446 (% style="margin-left: 60.0px;" %) 447 -[[ Bulk Operation - How to Perform a Batch Delete>>doc:Bulk Operation - How to Perform a Batch Delete(v12\.x)]]478 +[[doc:Bulk Operation - How to Perform a Batch Delete]] 448 448 449 449 (% style="margin-left: 60.0px;" %) 450 -[[ Bulk Operation - How to Perform a Batch Product Change>>doc:Bulk Operation - How to Perform a Batch Product Change(v12\.x)]]481 +[[doc:Bulk Operation - How to Perform a Batch Product Change]] 451 451 452 452 (% style="margin-left: 60.0px;" %) 453 -[[ Bulk Operation - How to Perform a Batch Status Change>>doc:Bulk Operation - How to Perform a Batch Status Change(v12\.x)]]484 +[[doc:Bulk Operation - How to Perform a Batch Status Change]] 454 454 455 455 (% style="margin-left: 60.0px;" %) 456 -[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe (v12\.x)]]487 +[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe]] 457 457 458 458 (% style="margin-left: 60.0px;" %) 459 -[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation - How to Perform a Batch UnsubscribeKill (v12\.x)]]490 +[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation - How to Perform a Batch UnsubscribeKill]] 460 460 461 461 (% style="margin-left: 60.0px;" %) 462 -[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users (v12\.x)]]493 +[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users]] 463 463 464 464 (% style="margin-left: 30.0px;" %) 465 465 **Target Audience Segments** 466 466 467 467 (% style="margin-left: 60.0px;" %) 468 -(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc: Utilities - TargetEngine(v12\.x)]]__499 +(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc:Segment Manager]]__ 469 469 __ 470 470 471 - 502 +\\ 472 472 473 - 504 +\\ 474 474 {{/expand}} 475 475 {{/panel}} 476 476 477 - 508 +\\ 478 478 479 - 510 +\\ 480 480 481 - 512 +\\ 482 482 483 - 514 +\\ 484 484 {{/layout-cell}} 485 485 {{/layout-section}} 486 486 {{/layout}}
- 11.__Review_the_Pre-Import_Summary.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.0 KB - Content
- 12.__Review_the_Sample_Mapping.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +16.9 KB - Content
- 3b.__If_not_using_an_Import_Mapping_Template__The_mapping.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.1 KB - Content
- 4._Proceed_to_the_mapping_section_and_map_your_fields___1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +90.0 KB - Content
- 5.__DO_NOT_SKIP_THIS_STEP_--_ALWAYS_CHECK_FOR_DUPLICATES_.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +45.7 KB - Content
- 6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +54.9 KB - Content
- 7.__Select_the_columnfield_in_your_import_file_to_specify.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +34.1 KB - Content
- 8.__To_link_media_files_for_a_record_to_the_folder_on_you.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +68.8 KB - Content
- Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.2 KB - Content
- Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +16.3 KB - Content
- media_1362667166234.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.3 KB - Content
- media_1366813790837.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.0 KB - Content
- media_1406494045151.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +1.3 KB - Content
- media_1443213231223.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +24.2 KB - Content
- media_1443213261172.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +24.4 KB - Content
- media_1443213294962.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.2 KB - Content
- media_1443213396710.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +44.0 KB - Content
- media_1443549296560.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.5 KB - Content
- media_1443551680910.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +559 bytes - Content
- media_1443551721550.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +3.7 KB - Content
- media_1443552112267.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +856 bytes - Content
- media_1443552145622.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +28.2 KB - Content
- media_1443552610096.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +41.6 KB - Content
- media_1443556620318.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +4.0 KB - Content
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -6 75351 +66546 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://info.onecount.net//wiki/spaces/OD/pages/6 7535/Import - How to Import a File(v12.x)1 +https://info.onecount.net//wiki/spaces/OD/pages/66546/Import - How to Import a File