Skip to Content

Changes for page Export Tool

Last modified by Rayaan Ahmed on 2026/04/07 10:36
From version 7.1
edited by Rayaan Ahmed
on 2026/04/07 10:36
Change comment: There is no comment for this version
To version 6.1
edited by Admin User
on 2025/06/27 12:14
Change comment: Migrated property [stableId] from class [Confluence.Code.ConfluencePageClass]

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rayaan
1 +XWiki.admin
Content
... ... @@ -2,9 +2,11 @@
2 2  
3 3  To start, choose Export Tool under Utilities on the Data Management Menu.  You will see a list of export jobs that are already in the system. Click Create New Export job in the upper-right corner to create a new export job:
4 4  
5 +\\
5 5  
6 6  [[image:attach:Export-job-list.png||width="1000"]]
7 7  
9 +\\
8 8  
9 9  Now you'll create your export job. First, give the job a name and a brief description. Next, choose which DExTr mapping you will apply to this export. These are the mappings you created in the [[DExTr>>doc:OCDEV.Utilities - DExTr -- OLD]] tool, also under Data Management.
10 10  
... ... @@ -16,21 +16,25 @@
16 16  
17 17  [[image:attach:User-Export.png||width="1000"]]
18 18  
21 +\\
19 19  
20 -Another type of export is **Transaction Export.** This option allows you to export data relating to product or package transactions that have been recorded in ONEcount. You may choose product OR package export, and you can choose the specific source code, product or package TERM that you would like exported. Please note that all of these options are// limiting //options. To export all transactions, leave the product, TERM and source code options blank.
23 +Another type of export is **Transaction Export.** This option allows you to export data relating to product or package transactions that have been recorded in ONEcount. You may choose product OR package export, and you can choose the specific source code, product or package TERM that you would like exported. Please note that all of these options are// limiting //options. To export all transactions, leave the product, TERM and source code options blank.
21 21  
22 22  Examples: To export all transactions used by a specific source code or codes, enter the codes you would like exported and leave the product/TERM options blank. To export all transactions for a product or TERM, choose the product(s) or TERM(s) and leave the source code field blank. Remember, these options are //limiting //options.
23 23  
24 24  [[image:attach:Transaction-Export.png||width="1000"]]
25 25  
29 +\\
26 26  
27 27  The third type of export is an **E-Mail Engagement Export. **With this option you can export e-newsletter engagement data from the system. When you choose e-mail export, you will need to pick the e-mail vendor for this export (the pull-down will show all of the e-mail systems that are configured for your system). Then you can select the newsletter list(s) or specific campaign(s) that you would like exported. Again these fields are limiting fields, so if you want to export e-mail engagement for all campaigns across all lists for a vendor, leave these fields blank.
28 28  
33 +\\
29 29  
30 30  [[image:attach:e-mail-engagement-export.png||width="1000"]]
31 31  
32 -Another type of export is** Web Engagement Export. **This exports web engagement data for all users across the entire ecosystem. There are no limiters for this export other than the date range export at the bottom of the screen.
37 +Another type of export is** Web Engagement Export. **This exports web engagement data for all users across the entire ecosystem. There are no limiters for this export other than the date range export at the bottom of the screen.
33 33  
39 +\\
34 34  
35 35  [[image:attach:Email-Engagement-Export.png||width="1000"]]
36 36  
... ... @@ -40,6 +40,7 @@
40 40  
41 41  [[image:attach:Banner-Export.png||width="1000"]]
42 42  
49 +\\
43 43  
44 44  Now choose whether the file should be accessed via FTP, SFTP, or URL. We recommend using SFTP or an HTTPS URL, since most imports involve some sort of PII. You will need to enter the full file path to your file, including the file name.
45 45  
... ... @@ -71,33 +71,8 @@
71 71  
72 72  When you are done, hit Save and your Import Job will be saved into the system. It will run the next time ONEcount scans your queue for jobs, and you'll receive an e-mail notifying you when the job is completed.
73 73  
81 +\\
74 74  
75 -=== **Note on Source Code Handling in Export** ===
83 +\\
76 76  
77 -For **export transaction types**, the source code is determined as follows:
78 -
79 -1. **Mapped Source Code in DExTr Mapper**
80 -1*. If a source code is mapped in the DExTr mapper, the system will export and add the source code based on that mapping.
81 -1. **No Mapping, but Source Code Field Present**
82 -1*. If no source code is mapped, but the source code field is included in the mapper:
83 -1**. The export job will check if there is any parent source code and add to file.
84 -1**. If the source code does not already exist in mapper or not in parent then source code id is added to file.
85 -
86 -=== **Note on Promo Code Handling in Export** ===
87 -
88 -For **export transaction types**, the promo code is determined as follows:
89 -
90 -1. **Mapped Promo Code in DExTr Mapper**
91 -1*. If a promo code is mapped in the DExTr mapper, the system will export and add the promo code based on that mapping.
92 -1. **No Mapping, but Promo Code Field Present**
93 -1*. If no promo code is mapped, but the promo code field is included in the mapper:
94 -1**. The export job will add the promo code id to the file.
95 -1**. If there is no promo code for that transaction then empty field is added to file.
96 -
97 -
98 -
99 -Tags:
100 -
101 -[[~[+~]>>url:https://xwiki.onecount.net/xwiki/bin/view/OD/Import%20Tool?showTagAddForm=true#xdocTags]]
102 -
103 -
85 +\\