By "Module Basic Settings" we are referring to the import, export, and header information, such as Customer Number. Some, or all of these, are necessary to allow the POS system to import the file.
Click on the Paradigm button to bring up the Paradigm page with the system settings.
(A) Version Information: The Last Update is the last revision date for Module specific features. The Source Version is the version of the data source that the XpressPOS Module is designed for. In the case of Paradigm, no version number is available.
(B) Import Settings: Set the default folder for Paradigm in the "Import File Path" box to C:\Program Files\Saberis\xpresspos2006\importfiles\. To do this, click on the ellispe button , and locate the folder. This will be the folder where the WTS Paradigm export file is written to. You can use any folder you want. It does not have to be the default one. The import file path has to be set to the folder that you are exporting the Paradigm XML document to.
The Import File Name is set to xpresspos.xml You must enter that file name in the XpressPOS box. You can use any name you want as long as you use the same name when you export the order from Paradigm.
If you use the “Select the import file at runtime” option, then you can use the “Save last Path” option. When this option is checked, the Import File Path will be re-set to the last folder that the user selected a file from.
This is particularly useful for the Paradigm Module which processes many different vendor quotation systems. It makes it easier to process if you are storing the data from the different vendors in different folders.
(C) Export Settings: XpressPOS allows for the optional naming of the export file name. Up to three (3) fields or properties can be concatenated (adding text fields together) to form the file name. For the this Module the available property sources are:
A Default Name
The Current Date
The Store Number
The Sales Person (number or name)
The default name is usually the best choice if the export file set under the POS button is on the user Desktop Computer. This is usually the case for Epicor Eagle and Falcon. It is also usually the case for the Spruce integration.
However, if the export file destination under the POS button is set to a server path (on premise or hosted) or the FTP transfer is used, then care must be taken to make sure one user does not "trample" on another user's file. Up until version 8.2.0, this has been done by adding a Store and/or Sales Person name or by making the default name unique for every user.
If you are running XpressPOS on a server and using VPN to access it, then export file naming became a problem. The solution was to change the name in the Summary form.
With XpressPOS version 8.2.0, there is a much better solution to all the "trampling" problems. Use a "composite" name.
To set-up a different export file name than the Default one, click on the Configure button beside the "You can modify the File Name or Extension".
In the first drop-down box, select the field or property you want to start the export file name with. In the second box, select the next property. Then finally the third if required.
Be aware that the file name can get very long and some systems have restrictions on the length of their import file names.
By having the User Name, the user can find the files on the POS system's files list quicker if there are a lot of orders waiting to be imported from different users. It also ensures that no other user will overwrite your file. This works whether XpressPOS in running on a Desktop or server computer.
XpressPOS knows what file extension is standard for the different systems and applies the correct one (.BMS, .BM6, .TXT, etc.). If needed, you can change them by selecting the "I will choose..." option.
NOTE for Falcon/Catalyst users: Your Falcon/Catalyst Administrator can setup the import to have a different extension for each XpressPOS Module (.and for Andersen, .OMS for Marvin, etc.). In the "I will choose my own extension" set the extension to match the Falcon/Catalys settings.
Remove illegal characters is for non-windows based systems. This option will purge blanks and other characters that will cause most UNIX/LINUX systems to throw an error on the import process.
(D) Data & Processing:
Some systems, such as ECS Pro and BisTrack, require a valid customer number in the import file. Select the "Use a default customer number" and enter one in the text box. Make sure the box for "I would like to send a Customer Number to my POS" is checked.