Import Custom Data

The majority of the data that resides in the device database is obtained from the sync server during synchronization.  There are, however, 4 types of data elements that can be defined using a separate import process.  The data types that can be imported are:

1. Unit price decimals
2. Credit card definitions
3. Country definitions
4. State and Province definitions

Import processing is triggered when a file named pflashimport.txt is placed in the \My Documents folder on the device.  When the application is started, the startup routines check to see if this file exists and, if it does, the Application Setup window is displayed.  Selecting the window's Setup action starts the import processing.  After processing has successfully completed, the import file is deleted.

The DPS PocketFlash™ installation includes a default import file that contains a default set of the 4 data types.  A copy of the default file can be found in the following location:

File location:
\Java\pocketflash\files
File name:
pflashimport.txt

When creating an import file, it is necessary to include only the data types you wish to define or redefine.  For example, to change the set of credit card types, create a file that only includes credit card definitions.  When the file is processed, only the credit card definitions in the device database are changed; none of the other data types are affected.

The import file is a plain text file and can be created or edited with any plain text file editor such as Notepad, WordPad or Word on a desktop or Pocket Word on the device.  The file consists of a series of semicolon delimited records.  The record format for each of the 4 data types are described below.

Unit price decimals
Defines the number of decimal positions for unit price data fields.

• Format:
  #PRCDEC;decimals
  Example:
  #PRCDEC;3
• #PRCDEC
  Required.  7 characters max.
  The import record id for unit price decimals.
• decimals
  Required.  1 number max.
  The number of decimals in a unit price data field.

Credit card definitions
Defines the types of credit cards that can be selected on the Order Payment window.

• Format:
  #CRCARD;code;name
  Example:
  #CRCARD;AMEX;American Express
• #CRCARD
  Required.  7 characters max.
  The import record id for credit card definitions.
• code
  Required.  5 characters max.
  The code associated with the credit card.
• name
  Required.  40 characters max.
  The name associated with the credit card.

Special processing is performed for codes AMEX, CART, DISC, DNRS, MSTR and VISA.  The descriptive names of these cards may be changed at will; however, the predefined codes must be used, where appropriate, in order for the cards to be included in special processing.  Other cards may be added as needed, but additional cards will not receive any special treatment other than mod10 check digit verification of entered card numbers.

Country definitions
Defines the countries that can be selected on the Customer Edit window.

• Format:
  #COUNTRY;code;name
  Example:
  #COUNTRY;CA;Canada
• #COUNTRY
  Required.  8 characters max.
  The import record id for country definitions.
• code
  Required.  5 characters max.
  The code associated with the country.
• name
  Required.  40 characters max.
  The name associated with the country.

State and Province definitions
Defines the states and provinces that can be selected on the Customer Edit window.

• Format:
  #STATE;country;code;name
  Example:
  #STATE;CA;AB;Alberta
• #STATE
  Required.  6 characters max.
  The import record id for state and province definitions.
• country
  Required.  5 characters max.
  The code for the country in which the state or province resides.
• code
  Required.  5 characters max.
  The code associated with the state or province.
• name
  Required.  40 characters max.
  The name associated with the state or province.

Important considerations:
If, after importing custom data, a DPS PocketFlash™ install is run on the device, your customized data will be overwritten with the default data that is included in the install.  You should therefore consider making a backup copy of your customized import file so that you can more easily reinstate your custom data after the install processing is completed.

See Also
Contents By Function
Contents By Window

 

---