You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This field allows the user to pass an array of time registration IDs. This links the registrations to the invoice line and updates their status to invoiced.
Currently, this field is missing from SalesInvoiceDetail / InvoiceDetail, but there's a bigger issue at play:
Because the JSON_FORCE_OBJECT option is used when generating JSON payloads, it is currently impossible to serialize a raw array into a request payload, it will always be converted to an object. It seems that the current design of this library simply does not support array fields.
Some kind of solution would be appreciated, although there probably is no easy solution here without serious structural changes.
The text was updated successfully, but these errors were encountered:
Same problem here for LedgerAccount.allowed_document_types. It's not possible to create a LedgerAccount. I only get the error below because allowed_document_types is an object instead of array.
Error 400: {"error":"Allowed Document Types isn't an array","symbolic":{"ledger_account":{"allowed_document_types":"array"}}}"
Is there a quick fix? Otherwise I'll see if I can make a pull request.
API Docs reference:
sales_invoice[details_attributes][time_entry_ids]
This field allows the user to pass an array of time registration IDs. This links the registrations to the invoice line and updates their status to invoiced.
Currently, this field is missing from
SalesInvoiceDetail
/InvoiceDetail
, but there's a bigger issue at play:Because the
JSON_FORCE_OBJECT
option is used when generating JSON payloads, it is currently impossible to serialize a raw array into a request payload, it will always be converted to an object. It seems that the current design of this library simply does not support array fields.Some kind of solution would be appreciated, although there probably is no easy solution here without serious structural changes.
The text was updated successfully, but these errors were encountered: