DK Plus exposes dynamic tables through /api/v1/general/table. Because table schemas differ, records are represented as read-only dictionaries while fixed metadata responses use DevOp-owned DTOs: TableChangeSummary and TableDeletedRecord.
List available fields before querying an unfamiliar table:
devop-dk table fields ARCUST
Read a bounded set of records from /api/v1/general/table/{name}/records:
devop-dk table records ARCUST \
--fields Number \
--fields Name \
--take 25
Fields may also be comma-separated:
devop-dk table records ARCUST --fields Number,Name --take 25 --json
The Cocona command parameter is string[] fields. Use the standard long option --fields (or short option -f) either repeatedly or with comma-separated field names:
devop-dk table records ARCUST -f ItemCode,Description --take 25
devop-dk table records ARCUST --fields ItemCode --fields Description --take 25
Apply incremental and key/value filters:
devop-dk table records ARCUST \
--fields Number,Name \
--modified-since 2026-10-01T00:00:00Z \
--key Number \
--value C-100 \
--take 100
Read one record with one or more query clauses:
devop-dk table record ARCUST \
--fields Number,Name \
--query Number=C-100
Inspect changes and deleted-record metadata:
devop-dk table changes ARCUST --modified-since 2026-10-01T00:00:00Z
devop-dk table deleted ARCUST --from 2026-10-01T00:00:00Z --take 100
All table list operations (table records, table changes, table deleted) are bounded by --take, which defaults to 100; they have no --all. Add --json to any command for automation-friendly output.
If DK Plus rejects a record request with HTTP 400, the CLI checks the table schema and reports unknown requested fields instead of printing a stack trace. Use devop-dk table fields <name> directly when exploring an unfamiliar table.
The CLI (table create, table update, table delete) and the PowerShell module (New-TableRecord, Update-TableRecord, Remove-TableRecord) write records through the generic table endpoints. Table values are dkERP text, so every value is a string; nothing is converted, which also keeps the commands independent of the current culture.
# Field values from repeatable --value Field=Value options (split on the first '='; empty values are sent as "")
devop-dk table create ARCUST --value Number=C-100 --value Name="Acme = Ltd"
# ... or from a flat JSON object of strings (--value and --file are mutually exclusive)
devop-dk table create ARCUST --file ./record.json --json
# Update names the key column(s) and the record's value with --key Field=Value (repeat for a composite key, in index order)
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
# Delete is the only table write that needs --yes
devop-dk table delete ARCUST --key Number --value C-100 --yes
New-TableRecord ARCUST -Value @{ Number = 'C-100'; Name = 'Acme = Ltd' }
Update-TableRecord ARCUST -Key @{ Number = 'C-100' } -Path ./changes.json
Update-TableRecord ARCUST -Key ([ordered]@{ Customer = 'C-100'; Number = '5' }) -Value @{ Name = 'Acme Ltd' }
Remove-TableRecord ARCUST -Key Number -Value C-100
create and update are ordinary writes and run directly, with no --yes (the cmdlets are Medium impact). delete requires --yes (exit code 2 and no request without it); Remove-TableRecord is High impact, and its confirmation target names the table, field, and value. DK Plus documents the delete action as performed at your own risk. Table mutations are never retried.
Input rules, checked before any request (exit code 2 in the CLI, DkPlus.InvalidArgument in PowerShell):
--value or --file, never both and never neither (-Value or -Path in PowerShell are separate parameter sets).--file or -Path document is one flat JSON object. A number, boolean, null, array, or nested object value is rejected, and the message names the field. A PowerShell hashtable value that is not a string is rejected the same way.delete needs a non-blank --key and --value.update names the record with --key Field=Value (PowerShell -Key @{ Field = 'Value' }), repeated, or an ordered dictionary, for a composite key. DK Plus identifies the record by the key column names in the request path, joined with ; in index order (Number, Customer;Number), and reads each key value from the request body. The commands send the names in the path and add every key Field=Value to the body next to the --value fields. A key field repeated in --value (or the file) must carry the same value, an update never changes a key field, and at least one other field must be set.
Record not found!. DK Plus updates the first row that has the key values, so a whole index that allows duplicates would change one of several rows; prefer a unique key such as RECORDID where the table has one.,, ;, * or =: the record filter reads them as separators and a wildcard, and the check below could not be exact. The command stops with exit code 2 (DkPlus.InvalidArgument in PowerShell) before any request.Update-TableRecord read the rows that match the key (at most two) and send the update only when exactly one matches. No match is a not-found error (exit code 2; PowerShell writes a non-terminating DkPlus.NotFound error) and several matches is an ambiguous-key error; neither shows row contents or key values. The check is a guard, not a lock: a concurrent writer can still add a matching row in between, and the read scans the table, so it can be slow on a large one.-Key accepts it only with one entry; use [ordered]@{ ... } for a composite key. DK Plus kept the fields left out of an update on the gift-certificate papers table SOPAPERS (verified on a test company); for any other table that is not verified, so try an update on a test company first.create and update print a success line (or, with --json, the record DK Plus returns, or null when it returns none); the cmdlets write the returned record as an object when there is one. Before 0.13.0 the key was a positional argument that never worked; see Upgrading to 0.13.
IReadOnlyList<IReadOnlyDictionary<string, string>> records =
await client.Table.GetRecordsAsync(
"ARCUST",
["Number", "Name"],
modifiedSince: DateTimeOffset.UtcNow.AddDays(-1),
maximum: 100,
cancellationToken: cancellationToken);
IReadOnlyList<string> fields =
await client.Table.GetFieldsAsync("ARCUST", cancellationToken);
TableChangeSummary? changes =
await client.Table.GetChangeSummaryAsync(
"ARCUST",
DateTimeOffset.UtcNow.AddDays(-1),
cancellationToken);
When GetRecordsAsync is called with maximum: null, with or without a key filter, the client reads the table in DkPlusClientOptions.PageSize batches instead of depending on the endpoint's 200-row default. A keyed read repeats the key filter on each request, so it has no row limit (before 0.13.0 it stopped at 10,000 rows with a warning). DK Plus returns RECORDMODIFIED even when it is not included in fields; after a full batch, the next request uses the last record's timestamp plus one millisecond as its modified cursor. The caller's requested field list is not changed. A missing, malformed, overflowing, or non-advancing cursor fails the complete operation, so an unlimited call never returns a partial list. A full batch whose rows are not in RECORDMODIFIED order (or lack a valid RECORDMODIFIED) is refused with DkPlusContractException, which names only the row position, because the next request starts after the last row and an older row would be skipped.
var allRecords = await client.Table.GetRecordsAsync(
"GECTRLS",
["KEY", "TEXT"],
maximum: null,
cancellationToken: cancellationToken);
await client.Table.UpsertRecordAsync(
"GECTRLS",
"KEY",
new Dictionary<string, string>
{
["KEY"] = "so-comment",
["TEXT"] = ""
},
cancellationToken);
UpsertRecordAsync reads at most two rows by the supplied key, creates when none exists, and updates when exactly one exists. Duplicate keys fail before writing. It is a client-side read followed by create or update—not an atomic server operation—so concurrent writers can race. The values dictionary should contain only the key and fields the caller intends to write; audit metadata should not be supplied.
The library's CreateRecordAsync, UpdateRecordAsync, and DeleteRecordAsync take the same string dictionaries and keys. UpdateRecordAsync(table, key, values) is unchanged and does not pre-read: its key is the column name(s) joined with ;, and the key values must be in values. Project delete (Project.DeleteAsync, devop-dk project delete, Remove-Project) uses the delete route on the dkERP project table pjjob, because DK Plus has no project DELETE endpoint.
DK Plus sends 1899-12-30 (as 1899-12-30T00:00:00.000Z) for "no date" in a table row. The generic Table resource returns the strings as sent. The typed table-backed resources read that value as null: Created and Modified of company settings and Modified of vendor groups, and the dates of gift certificates and credit notes. Every other date is kept.