When retrieving branch orders, the field order.branchOrderNumber will be filled, instead of order.orderNumber.
The fields article.colourSequenceNumber and article.sizeSequenceNumber have been added, this designate the position of the colour and size in the colour list and the size list, respectively.
Saving the field extRelationId now works correctly.
The API now checks if a valid siUnit is supplied when using createProduct and updateProduct. An invalid value will trigger a SOAP fault that explains this.
New function for retrieving packing slips: getPackingSlips
New API functions for managing activities:
getActivitiescreateActivityupdateActivitydeleteActivityAlso added the following properties:
receipt.activityIdinvoice.activityIdorder.activityIdproposal.activityIdpackingSlip.activityIdAnd the following filter properties:
getReceipts(activityId)getInvoices(activityId)getOrders(activityId)getProposals(activityId)The line.data now also contains (when applicable) cancelledQuantity and cancelledDecimalPlaces to return how much of an order line has been cancelled.
New function for retrieving cashdrawer balancing moments: getCashDrawerBalancingList
New V2 of the functions savePurchaseOrderV2 and savePurchaseDeliveryV2 where purchasePrice is a string instead of an int64. This allows for decimal values with more than two decimal places.
New V2 of the functions getPurchaseOrdersV2 and getPurchaseDeliveriesV2 that also return purchasePrice as a string instead of a int64 .
All functions that return relationNumber and relationName, now also return relationCategoryId and relationBankAccountNumber (e.g. getOrders, getReceipts, getInvoices).
The function getOrder now also returns a filled-in paymentList (as long as actual order down payments were made of course).
When articles, relations or employees have more than 117 cards fields, the creation or updating of these cards through the API did not work.
v1.9.0 // © Mplus Software 2014 - 2025