Support
- Advanced Backup
- Client Side
- Cloud Enterprise
- ColdFusion
- Control Panel
- cPanel
- Customer Portal
- DNS Information
- Dedicated Servers
- DirectAdmin
- Domain Name
- dotDefender
- Dreamweaver
- FileCatalyst
- Front Page
- FTP
- General Information
- Hosted Exchange & SharePoint
- IIS6
- IIS7
- Juniper Netscreen Firewalls
- Linux
- List Server
- MIVA Merchant
- Addattribute
- Addcategory
- Addproduct
- Adminlockout
- Assigncategory
- Basicguide
- Batchorders
- Changeimageprod
- Createstore
- Disablecustomeraccount
- Encryptorders
- Expiredshoppingbaskets
- Exportdata
- Imagetypes
- Imerchant
- Integratedreamweaverandmiva
- Mailserver
- Movestore
- Nonsecure
- Packdatafiles
- Paymentgateways
- Processorders
- Removecreditcard
- Reorder Products
- Securestore
- Simplevalidation
- Ssl
- Testpurchase
- Toplink
- Upgradewizard
- Welcomemessage
- Miva5
- Add a Site Map in Miva 5.5
- Availability Groups in Miva 5.5
- Calculating Shipping Charges in Miva 5.5
- Creating Meta Tags with Miva 5.5
- Create Store Administration Groups in Miva 5.5
- Create the Main Store in Miva 5.5
- Set up Customer Accounts in Miva 5.5
- Delete Expired Baskets in Miva 5.5
- Existing Web Site Integration In Miva 5.5
- Export Orders to a Flat File (.dat)
- Give Customers the Best Price with Price Group Overlap Resolution in Miva 5.5
- Launchpad Configuration in Miva 5.5
- Logging Affiliate Payouts in Miva 5.5
- Logging and Statistics in Miva 5.5
- Overview of Miva Merchant 5.5 Admin Page Options
- What are "Modules" for Miva
- PayPal SDK v4.31 Changes
- Put a Search Box on Every Page in Miva 5.5
- Replace Navigation and Shopping Buttons in Miva 5.5
- Run an Affiliate Program in Miva 5.5
- Take the Store Offline in Miva 5.5
- Template Structure in Miva 5.5
- Void Specific Affiliate Earnings in Miva 5.5
- Price Groups in Miva 5.5
- Determining the Database Your Miva Store is Using on Linux
- Preventing Malicious Login Attempts to Your Miva Administrator
- MySQL
- Patching / Server Updates
- phpMyAdmin
- Plesk
- Policies and Procedures
- Premium Spam Filtering
- Programming
- Ruby on Rails
- Search Engine Submission
- SharePoint 3
- SharePoint 2010
- SiteDesigner
- SmarterMail 3
- SmarterMail 4
- SmarterMail 5
- SmarterMail 6
- SmarterMail 7
- SmarterStats
- SmarterTrack
- SQL Server
- Secure Socket Layer (SSL)
- Uploading Your Website
- Video Tutorials
- Windows Server 2003
- Windows Server 2008
- Web Design
- WordPress
- Advanced Monitoring
- MediaWiki
- Enkompass
- Microsoft Outlook 2010
- Android
- Outlook Web Access
- Critical Availability Service
- NAS Data Transfer
- Customer Portal Demos
- Joomla
- Moodle
- Cloud Dedicated
- Gallery CMS
- phpBB
- Standard Monitoring
- Righteous Restore
- NAS (Network Attached Storage)
- Networking
- SmarterMail 8
- PCI Security Scan
- LinkTiger
- Windows Cloud VPS
- Linux Cloud VPS
- Linux VPS
- Windows VPS
- Hyper V
- ENSIM
- Alert Logic
- Webmin
- e107
- Vbulletin
- VPN
- Visual Vault
- Mozilla Thunderbird
- PyroCMS
- Active Directory
- Vmware Related
- Drupal
Export Orders to a Flat File (.dat)
Exporting orders to a flat file is a simple process. Retrieving the data file requires an FTP or remote connection to the server. You may need to check with your host for the available options.
Remember—only batched orders can be exported this way. All orders you back up should already be processed (completed).
The exported orders file will not include payment data.
- In the Admin Menu, click the + next to the store's Utilities link
- Click the + next to Export Data
- Click the Export Orders To Flat File link
- In the Batch to Export pull-down menu, select the batch you want to export. Optionally, you can opt to export all orders in the store, or all unbatched orders
- If you want, enter a different name for the export file. By default, the file name will be orders.dat
- Choose the delimiter.
-
Choose whether you want to replace any existing data or if you want to append the batch to existing data
- Click the Export button
-
Repeat steps 4-5 for each subsequent batch you'd like to export that is listed in the pull down Menu
By default, the orders.dat file (the default file name for exported orders) is tab delimited. This means the text file will contain a TAB SPACE between each field in the orders records. Tab-delimited files can usually be opened by any common spreadsheet or database program. However, you can tell Miva Merchant to use a different delimiter, such as a comma or the pipe character.
By default, each exported batch will append to the existing orders.dat file. This means any orders you export next week will automatically be added to the existing file, which includes orders exported today. If you choose Replace File, then any previous exports to this specific file will be overwritten.
Should I append or replace data?
Let's say you want to export orders on a weekly basis and import them into Microsoft Excel for analysis. On week one, you export batches for days 1-7, choosing to append the data to the orders.dat file. The next week, since you've already imported the information into the first spreadsheet, you export days 8-14, and choose Replace file, since you only need the information for these particular days (the others are already in the offline spreadsheet).
In this case, each week when you export, you will choose Replace file for the first batch listed, and Append for each thereafter until all seven days are exported.
Now let's say you want to export orders every week, but you want to keep a different .dat file for each on the server. In this case, you would enter a different file name for the exported orders.
Either way you choose, you are able to export each week, even when you batch each day, and import your data into Excel for analysis.
