On this page
PalmOrder formats consist of mobile-application configuration, incoming tables from the accounting system and documents created on a device.
Configuration
| File | What it defines |
|---|---|
exchange.xml | Exchange profiles, documents, tables and ordinary files. |
preferences.xml | Application settings the integrator prepares for remote application. |
tables_columns.xml | Column titles, order, visibility and display format in tables. |
custom_tables.xml | Additional tables and their main menu titles. |
print_forms.xml | Printer forms and their templates. |
pdf_forms.xml | PDF forms and their HTML templates. |
Every parameter must match the current behavior of the Android application and PalmOrder Server. See exchange.xml for a detailed description of the profiles.
XML tables
A table file has a <table> root element, a <schema> section with fields and a <data> section with records. The file's actual encoding must match the encoding value in the XML declaration.
The order of <f> values in every <record> must exactly match the order of fields in <schema>. See XML tables for the full description.
Data schemas and relationships
| Section | Contents |
|---|---|
| Value lists | Price categories, payment and delivery types, trade points. |
| References and routes | Products, customers, individual prices, hierarchy and visit schedules. |
| Document schemas | Fields in orders, payments, store-checks and debts. |
| Service settings | gl_settings and the application's administrative settings password. |
| Custom tables | Additional reports, their data and menu entries. |
Documents
A document has a header and can have one table section:
- every
<document>inexchange.xmlallows no more than onedocTable; - a document without lines may not have
docTable; - the output XML for such a document contains no more than one
<table>element with lines.
See Documents from devices for the structure of incoming XML files. See First exchange for a practical configuration and received-order example.