Work Orders

Work order page services are the core of the AMZS mobile application. They manage the full lifecycle of field service work orders, from creation through completion and invoicing.

AMZSMobileWorkOrders

Namespace: urn:microsoft-dynamics-schemas/page/amzsmobileworkordersEndpoint: Page/AMZSMobileWorkOrdersType: Full CRUD Read key: No (String)

Custom Method

This service exposes an additional custom method Delete_Work_Order_Instr_Line beyond the standard CRUD operations.

Key Entity Fields

The entity contains approximately 120 fields. The most important ones are listed below:

Field	Type	Description
Key	String	NAV internal key
No	String	Work order number (primary key)
Order_Type	Enum	Type classification of the work order
Status	Enum	Current processing status
Work_Order_Status	Enum	Operational status of the work order
Customer_No	String	Associated customer number
Customer_Name	String	Customer display name
Chassis_Code	String	Vehicle chassis code
Vehicle_Description	String	Description of the vehicle
Resource_No	String	Assigned resource number
Performer_No	String	Assigned performer number
Order_Date	Date	Date the order was created
Posting_Date	Date	Date for accounting posting
Amount	BigDecimal	Order amount excluding VAT
Amount_Including_VAT	BigDecimal	Order amount including VAT
Responsibility_Center	String	Organizational responsibility center
Registration_No	String	Vehicle registration plate number
Mileage_Start	String	Odometer reading at start
AKC_Booking_Entry_No	String	AKC booking reference
AKC_Work_Order_No	String	AKC work order reference

Additional Fields

The full entity includes approximately 100 more fields covering GPS coordinates, location data, timestamps, and extended metadata. Consult the SOAP WSDL for the complete schema.

---

XMLWorkOrder

Namespace: urn:microsoft-dynamics-schemas/page/xmlworkorderEndpoint: Page/XMLWorkOrderType: Full CRUD Read key: No (String)

Custom Method

This service exposes an additional custom method Delete_Work_Order_Line beyond the standard CRUD operations.

This is an extended work order representation with approximately 196 fields, including inline work order lines. It is used for full work order management operations where the complete data set is needed in a single request.

Large Payload

Due to the ~196 fields and inline line items, responses from this service can be large. Use targeted ReadMultiple filters to minimize data transfer.

---

MobileWorkOrderLines

Namespace: urn:microsoft-dynamics-schemas/page/mobileworkorderlinesEndpoint: Page/MobileWorkOrderLinesType: Full CRUD Read key: Document_No (String), Type (Enum), No (String)

Entity Fields

Field	Type	Description
Key	String	NAV internal key
Type	Enum	Line type (Item, Resource, etc.)
No	String	Item or resource number
Description	String	Line item description
Description_2	String	Extended description
Location_Code	String	Inventory location code
Quantity	BigDecimal	Ordered quantity
Reserved_Quantity	BigDecimal	Reserved stock quantity
Qty_on_WO_Shipment	BigDecimal	Quantity on work order shipment
Unit_Price	BigDecimal	Price per unit
Unit_Cost_LCY	BigDecimal	Unit cost in local currency
Commercial_Discount_Percent	BigDecimal	Commercial discount percentage
Member_Discount_Percent	BigDecimal	Membership discount percentage
Line_Amount	BigDecimal	Total line amount
Qty_to_Ship	BigDecimal	Quantity to ship
Quantity_Shipped	BigDecimal	Quantity already shipped
Qty_to_Invoice	BigDecimal	Quantity to invoice
Quantity_Invoiced	BigDecimal	Quantity already invoiced
Amount_Including_VAT	BigDecimal	Line amount including VAT
Note	String	Line note or remark
Business_Relation	Enum	Business relation type
Document_No	String	Parent work order document number

---

AMZSMobileWorkOrderLines

Namespace: urn:microsoft-dynamics-schemas/page/amzsmobileworkorderlinesEndpoint: Page/AMZSMobileWorkOrderLinesType: Full CRUD Read key: Document_No (String), Type (Enum), No (String)

INFO

This service has the same entity structure as MobileWorkOrderLines but uses a different NAV endpoint. It may expose a different subset of data or apply different business logic on the NAV side.