System Control > Customer Load > Select Records to Extract from QAD EA
Select Records to Extract from QAD EA
To extract the data you need to:
1
Choose the domain with customer records you want to load.
2
Enter the customer attribute to use for selecting records in the first field. The choices are customer ID, name, site, type, region, promotion group, and date added.
3
Choose an operator from the list: =, <>, <, <=, >, >=.
4
Enter the value you want to match on, such as region = West. You must determine these values from QAD EA, since your input is not validated on the Customer Load screen.
5
Select a command to continue or end the current query.
6
Indicate if records should be appended to an existing CSV file.
•
When this check box is selected, the records that match the specified selection criteria are added to the bottom of the last set of records you extracted. You can use this to build a master list based on several different queries.
•
When this check box is not selected, a new CSV file is created. If you have not loaded the previously extracted values into QAD CSS, they are lost. Use this for a new query or when you want to discard the results of a query because they are not what you expected.
Note: If you want to maintain individual query results, save the files in a work area-using the CSV format-with unique names before executing a new query.
7
Click Extract QAD EA Records. The system extracts records based on the query you have created and displays them in an Excel spreadsheet named Customers.csv.
8
Save this spreadsheet with a unique name to a local drive or your network file share. If you are working with multiple files, include a data and time stamp to ensure file uniqueness, such as WestRegionCusomers092004.csv.
Note: If you execute multiple queries and append the data, the results may include duplicate records. You should sort the data by customer ID and ensure there are no duplicates before loading. When duplicates exist, the values from the last record loaded will apply if the load is done with overwrite update; otherwise, errors will result from the duplicate records.