Partial updates result in resetting values in EOL about exactonline-api-dotnet-client

[shtrip]

Which property did you use to update the amount? As far as I know the amount can't be changed directly, it is calculated from price, quantity and discount.

Indeed PATCH would be the correct verb for partial updates but the current implementation of the service is handling this through PUT requests.

[martijnboland]

My bad, I meant quantity instead of amount.

[shtrip]

My test application is failing to cooperate so I'm having some trouble reproducing this. A test using Postman worked fine, the unit price and discount were not cleared.

Did you do a GET on the SalesOrderLine after updating the quantity ? Did you also check these values in the Exact Online web application ?

[martijnboland]

I checked in the Exact Online web application. I'll try if I can reproduce
an example PUT request.

On Friday, April 17, 2015, shtrip [email protected] wrote:

My test application is failing to cooperate so I'm having some trouble
reproducing this. A test using Postman worked fine, the unit price and
discount were not cleared.

Did you do a GET on the SalesOrderLine after updating the quantity ? Did
you also check these values in the Exact Online web application ?

—
Reply to this email directly or view it on GitHub
#7 (comment).

[martijnboland]

The following json payload is generated by the client sdk when only the quantity of a SalesOrderLine has changed:

{
    "AmountDC": null,
    "AmountFC": null,
    "Quantity": 2.0,
    "QuantityDelivered": null,
    "QuantityInvoiced": null,
    "UnitCode": null,
    "VATAmount": null,
    "VATCodeDescription": null,
    "VATPercentage": null
}

After this, the Unit price and net price are reset to 0.00.

[shtrip]

Thanks, this is very clear. Only the Quantity should be in there. This is a bug.

[shtrip]

This is fixed through pull request 57.