iVendNextDevelopers Request a sandbox

A transfer, a delivery or an invoice made from its request or order

The customer asks: Our service makes the stock transfer from a material request, or the delivery note or invoice from a sales order, as Desk's Create menu does

What you build

From POS build 2.0.0.654, your service calls /api/method/ivendnext_mpos.api.v1.material_request_to_stock_entry, sales_order_to_delivery_note or sales_order_to_sales_invoice with the submitted source's name. Each answers an unsaved document built as Desk's Create menu builds it; your service checks or changes it, then saves it with POST /api/resource/<record type> (api/README.md).

Limits

Tell the customer

Our service makes the transfer, the delivery or the invoice from your request or order exactly as Desk would, and a person, or our service, then saves and submits it.

What next

  1. Tell the customer the 3 limits above, and write them into the proposal.
  2. Start from: The generic kit — an API description and a request collection.
  3. Build and test it on your sandbox (request one if you have none; what is on it).
  4. Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
  5. Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.

Stop your service for a while and start it again: it must catch up from the event feed, missing nothing.

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit