0.13.0 has two breaking changes and one behavior change. The new gift-certificate features are described in
Gift certificates and credit notes and in the
release notes.
devop-dk table update takes the record through repeatable --key Field=Value options (the key column and the record's value,
in index order for a composite key) instead of a positional key value. The old form never worked, so there is no
replacement for it.
# Before (0.12.0 and earlier): devop-dk table update ARCUST C-100 --value Name="Acme Ltd"
devop-dk table update ARCUST --key Number=C-100 --value Name="Acme Ltd"
devop-dk table update ARCUST --key Customer=C-100 --key Number=5 --file ./changes.json
In PowerShell, Update-TableRecord -Key is a dictionary of key column names and values instead of a string. Use an
[ordered] dictionary for a composite key; a plain hashtable is accepted only with one entry.
Update-TableRecord ARCUST -Key @{ Number = 'C-100' } -Value @{ Name = 'Acme Ltd' }
--value, -Value or the file only with the same value, and at least one other field must be set.,, ;, * or = is refused before any request, because DK Plus reads them as a pattern or aSee Generic tables.
IDkPlusSalesResource gains GiftCertificate and CreditNote, and IDkPlusSalesInvoiceResource gains
CreateWithGiftCertificatesAsync and FindByReferenceAsync.
IDkPlusClient is not affected.NotSupportedException, so an implementation built againstnetstandard2.0 asset, where the members are abstract: add them before the implementation compiles or loads against 0.13.0.IDkPlusGiftCertificateResource.MarkUsedAsync and IDkPlusCreditNoteResource.ActivateAsync are plain members, because thoseA date that DK Plus leaves unset (0001-01-01 in JSON responses; 1899-12-30 in JSON responses and in the typed
table-backed resources such as company settings and vendor groups) now reads as null instead of a real date in the year 1
or 1899. Code that compared a date with those sentinel values should test for null instead. The generic Table resource
still returns the strings as sent.
Table.GetRecordsAsync with a key filter and no maximum reads every matching row instead of stopping at 10,000 with aRECORDMODIFIED order instead of silently skipping rows.SalesInvoiceCreateOptions.OriginalPrices (--original-prices, New-Invoice -OriginalPrices) wasOriginalPrices; see