Batch Update Api (Invoice)

This mixin reloads the full object using the queryset the default mixin removes all the select related, causing issues with serializers that contains data from different entities. That way we use the queryset defined. We should use this update mixin in all places with prefetches, mainly with custom fields. The issue in the original implementation, is that when the object gets saved, and all the prefeetches are dropped So the serializer of the response has to re query everything, and if we have lists to process, it does N+1

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Allows a serializer to get a user "change comment" in the update requests and uses that which is later used to set the Revision comment. Changes due to creation / deletion are not tracked at the moment.

boolean | null
string
Defaults to pending
invoice_items
array of integers
invoice_items
string
string
string | null
date | null
date-time | null
date | null
integer
required
integer
required
integer
required
integer | null
Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Response

Language
Credentials
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json