B.3. file fields – Gasboy Fleet Head Office System User Manual
Page 331
329
B.3. FILE FIELDS
The first three fields in all lines in every file should be as follows:
a.
Action – The type of action intended on the line in the list:
• The letter "A": to add a new entity, line will be rejected in case the entity already
exists.
• The letter "U": to update an existing entity, line will be rejected in case the entity
doesn’t exist.
• The letter "R": to add a new entity or update an existing one (Recommended)
• The letter "D": to delete an existing entity. When sending a delete command, only
the unique keys are to be used and only in the order described below. The
following sample record layouts show the required fields for each record type:
Mean: D,Mean,name,string
Department: D,Dept,fleet-name,dept-name
Fleet: D,Fleet,name
Group Rule: D,GroupRule,name
Rule: D,Rule,name
Model: D,Model,name
• The letter "P": To update an existing device (mean). The vehicle number (license
plate number) is used as the key of the current record for this line only.
NOTES
The option to rename an existing unique key is
currently not available (see list of unique keys in
each table).
b.
Record_Type – Type of entity, need to be typed exactly
c.
Name – Entity Name, need to be typed exactly
All fields should be typed exactly and in the correct order, as described below. Not all fields are
mandatory; nevertheless, in order for the system to recognize the fields, a comma or an empty cell
should be inserted for any empty field. For example, a device line containing only mandatory fields
should look as follows in a text file format:
name,status,type,hardware_type,auttyp,employee_type,plate,string,,department
_name,,,Price_list_name,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,num_ofstrings,,,,,,,,
FMS and FHO User’s Manual - MDE-4821