Release date: 2026-11-11.
The NuGet packages DevOp.ERP.Abstractions, DevOp.DK.Plus and DevOp.DK.Plus.Cli and the PowerShell module DevOp.DK.Plus share this version.
Live verification. Verified live on a test company (2026-11-11) with this release: selling gift certificates (including automatic numbering, required barcodes and expiry), redeeming them with cash change, forfeit and a credit-note change, marking certificates used, activating the change credit note, the recovery commands, and the refusals before any write; every test invoice ended fully settled. Not exercised live: the reference lookup after a failed invoice create, because no create failed.
client.Sales.GiftCertificate and client.Sales.CreditNote provide Query() (only ModifiedSince applies), GetAsync(number), GetByBarcodeAsync (certificates), GetByRecordIdAsync, and CountAsync(). GiftCertificate.IsRedeemable(now) tells whether a certificate can still be spent, and GetSettingsAsync() returns the company's gift-certificate settings and payment types. CountAsync() is an exact count made with ordinary paged reads and has no row limit; the queries cannot count. A number or barcode that is blank or contains *, =, , or ; is rejected before any request.client.Sales.Invoice.CreateWithGiftCertificatesAsync(request, options) checks each certificate, computes the invoice total, creates the invoice, and marks every certificate used.
UnitPrice with PricesIncludeTax = true, a quantity other than 0, and no discount, and its quantity times unit price must be a whole number of cents. OriginalPrices is refused. A line that breaks a rule is a DkPlusModelValidationException keyed by its position, before any request.DkPlusGiftCertificateInvoiceException with the outcome Created. The certificates are marked used, because their payments are on the invoice; a change credit note and sold certificates are held as pending steps with the reason AmountMismatch. Correct the invoice in dkERP before completing a held step.Cash, CreditNote, or Forfeit. With Forfeit the result's Change is the forfeited amount, not an amount paid back.GiftCertificatePaymentId, ChangePaymentId). The client checks them before any write against the company's payment modes in the dkERP table SORUPM (an active type 9 for certificates, type 6 for cash change, type 8 for credit-note change), not against the payment-type endpoint, whose index can lag.Reference of 1 to 12 letters and digits (with -, _ or . between them). Nothing is retried or rolled back: a step left after the invoice exists throws DkPlusGiftCertificateInvoiceException with the pending steps.Sales.GiftCertificate.MarkUsedAsync(recordId, invoiceRecordId), Sales.CreditNote.ActivateAsync(recordId, invoiceRecordId, invoiceNumber), and Sales.GiftCertificate.CreateAsync(request) (the request needs SourceInvoiceNumber) finish a step and are safe to repeat; client.Sales.Invoice.FindByReferenceAsync(reference) lists the posted invoices with a reference, to check an invoice whose outcome is unknown before creating it again.GiftCertificateInvoiceOptions.Sell, alone or together with redemption.devop-dk sales gift-certificate get, list, count, settings, mark-used and create; sales credit-note get, list, count and activate; sales invoice find --reference; and the --gift-certificate, --gift-certificate-payment-id, --change, --change-payment-id and --sell-gift-certificate options of sales invoice create, which need --post --yes. Redeeming needs every line priced with tax (-p <price> --prices-include-tax). sales credit-note activate needs --invoice-number and sales gift-certificate create needs --source-invoice-number. A pending step, or a created total that differs from the computed one, exits with code 1 and a JSON partial result with --json, and stderr names the command that completes the step.Get-GiftCertificate, Get-GiftCertificateCount, Get-GiftCertificateSettings, Get-CreditNote, Get-CreditNoteCount, Set-GiftCertificateUsed, Enable-CreditNote, New-GiftCertificate (-SourceInvoiceNumber is required), the gift-certificate parameters of New-Invoice (-Post:$false is refused with them), and Get-Invoice -Reference.Table.GetRecordsAsync with a key filter and no maximum reads every matching row instead of stopping at 10,000 with a warning. It pages like an unfiltered read and repeats the key filter on each request.RECORDMODIFIED order, instead of silently skipping rows.SalesInvoiceCreateOptions.OriginalPrices, sales invoice create --original-prices and New-Invoice -OriginalPrices said the opposite of what DK does. With the option DK prices every line from the product (its price lists and discounts); without it DK keeps the price you supply, and a line without a price is invoiced at 0.0001-01-01, and DK's minimum date 1899-12-30) now reads as null instead of a real date in the year 1 or 1899. Examples are DueDate, InvoiceDate and ReceivedDate of purchase invoices.1899-12-30) now reads as null in the typed table-backed resources: Created and Modified of company settings and Modified of vendor groups. The generic Table resource still returns the strings as sent.devop-dk table update and Update-TableRecord now work: the key column names go in the request path and the key values in the body, as DK Plus requires. Both read the matching rows first and send nothing unless exactly one matches (no match is a not-found error, several matches an ambiguous-key error). Name the key columns of a whole index, in index order.devop-dk table update takes repeatable --key Field=Value options instead of a positional key value (devop-dk table update ARCUST --key Number=C-100 --value Name="Acme Ltd"). In PowerShell, Update-TableRecord -Key is a dictionary (-Key @{ Number = 'C-100' }; an [ordered] dictionary for a composite key). A key value containing ,, ;, * or = is refused.IDkPlusSalesResource gains GiftCertificate and CreditNote, and IDkPlusSalesInvoiceResource gains CreateWithGiftCertificatesAsync and FindByReferenceAsync. They are default members on .NET 10 and abstract on every other target, so an own implementation of either interface must add them there.See Gift certificates and credit notes for the full guide and Upgrading to 0.13 for the breaking changes. Back to release notes.