The fsreqValTruck type exposes the following members.
Action if the truck does not exist and is created.
Indicates if this command should be logged to the database. The command must be of a type that supports logging to the database in order to take effect. Currently the commands supporting this option are: TFSCut(Inherited from fsreqCommand.)
If the truck does not exist and is created: The capacity of the truck.
If the truck does not exist and is created: The carrier.
A GUID identifying this particular XML command. If a command fails due to a communication failure the client has no way of knowing if it has been processed. Each command that makes changes (as opposed to just retrieving data) will check the CommandGUID against the GUIDs that have already been processed. If the GUID has already been processed then it will not be re-processed and instead return with an error. This allows the client to saftely re-try a failed command without risking unintended changes.(Inherited from fsreqCommand.)
If the truck does not exist and is created: The destination of the load. Intermediate Destination: Company code of the intermediate shipping destination. Jobsite: Blank or 'Jobsite'
If the truck does not exist and is created: The name of the firm that the load is being shipped from.
If the truck does not exist and is created, and the destination is an intermediate location: Indicates if the material on the load is going to be returned to the shop before being shipped to the jobsite.
If the truck does not exist and is created: The trailer number of the load.