DevOp.DK.Plus.Cli 0.5.0

This package has no dependencies.

v0.5.0: the fluent list commands (customer, customer transaction, customer group, product, product group, product category, product unit, employee, sales invoice, order, quote and recurring, sales person, payment mode, term and type, currency, project) gain --all, which reads every record page by page, and --yes (-y). --all cannot be combined with --take and exits with code 2 before any request when both are given. Breaking: --take now accepts 1-1000 on these commands (0.4.2 allowed up to 10,000; the default is still 100) and exits with code 2 before any request above that; use --all to read more. --all asks first on stderr (Fetch every customer? ... [y/N]) because it can move a lot of data; --yes skips the question, and with redirected stdin, stdout or stderr and no --yes the command stops with exit code 2 naming --yes. customer transaction list-for, project all and project work-request list-for always read every record, so they now ask the same way and take --yes. With --json the fluent lists now stream one array record by record; a failure or Ctrl+C after the first page leaves a truncated array on stdout with a non-zero exit code. --include and --exclude (repeatable or comma-separated) narrow the returned properties on the customer, product, customer transaction, customer group, product group, employee, sales invoice, order, quote and recurring, and payment mode, term and type lists; unknown names, sensitive employee fields in --include and identity properties in --exclude exit with code 2 before any request, and a table under --include shows only the named columns. customer list gains the server-side filters --name, --sales-person, --country, --postal-code, --payment-term, --payment-mode, --email, --blocked, --vat-exempt and --deleted, and product list gains --alias-item-code, --inactive, --on-web and --deleted. Text filters and --group are sent lowercase and --country uppercase, and --name without * is a contains search. An ArgumentException error no longer ends with .NET's (Parameter '...') suffix. The boolean filters take a value (--blocked false) because Cocona would read a bare bool option as a flag and ignore a following false; omitting one sends nothing. How DK Plus matches the filter values is not verified live (products document * as a wildcard). New 'table create', 'table update' and 'table delete' write records of any dkERP table through the generic table endpoints: create and update run directly, delete needs --yes; what the key of 'table update' (the record to change) means is not verified live. New 'project delete [number] [--record-id N] --yes' deletes a project by number or record id through the generic table endpoint on pjjob, because DK Plus has no project delete endpoint; the maintainer confirmed that the table name and both key names work; it bypasses DK Plus project validation and its effect on projects with transactions, phases or work requests is not verified live. Give exactly one of the number or --record-id (otherwise exit code 2 before any request); without --yes it exits with code 2 and sends nothing. On Windows, the stored login token now lives in the non-roaming %LOCALAPPDATA%\DevOp\devop-dk folder with an owner-only access control list (a token stored by an earlier version in %APPDATA% is moved on first use, and logout removes both). Update the CLI and the module together: the first read by a new version moves the token, and a 0.4.2 CLI or module reads only the roaming %APPDATA% copy, so it no longer finds the login. Writes of config.json and the token retry briefly when another process holds the file. On every OS, saved file names that are Windows device names (CON, NUL, COM1, ...) get a _ prefix (an attachment named con.pdf is saved as _con.pdf on Linux too). v0.4.2: new sales create commands. 'sales invoice create' builds an invoice from --customer and the single-line options (--item-code, --quantity, --unit-price, ...), from repeatable --line "item-code=A;quantity=4;unit-price=1000" options, or from a --file; --post posts it and requires --yes. 'sales order|quote|recurring create' create the head only (a --file with Lines is rejected) and DK Plus auto-creates a missing customer unless --no-auto-create-customer is set. 'sales order|quote|recurring lines create' add one line. On every create, --file cannot be combined with the direct options, and numbers and dates parse culture-independently. New config setting salesPerson ('devop-dk config set salesPerson S-1'): the default salesperson for sales creates after --sales-person; a --file document's own value wins; without either, DK Plus uses the API user's sales person. v0.4.2: purchase invoice approval --file now rejects a document without ApprovalAction (for example {} or one with only a Description) with exit code 2 and a validation error naming ApprovalAction, before any request is sent; before, the missing value was sent as ApprovalAction 0. v0.4.2: fixes error reporting for failures the client raises before or without contacting DK Plus: a request-model validation failure now exits with code 2 and lists the rejected members instead of reporting that the DK Plus API could not be reached, authentication and authorization failures exit with code 1 with the login hint, and a missing connection, timeout, open circuit, or local concurrency limit has its own message; only real transport failures print the network message. v0.4.1: sales order, sales quote and sales recurring gain update and delete, and a lines group with lines update and lines delete, for v2 documents by UUID and line sequence. update takes direct fields or a sparse SalesOrderUpdateRequest, SalesQuoteUpdateRequest or RecurringSaleUpdateRequest --file; lines update takes direct line fields (--item-code, --quantity, --unit-price and others) or a sparse SalesDocumentLineRequest --file, whose top-level Sequence is rejected because the sequence is the argument. --date, --valid-from and --valid-until take an ISO 8601 date (yyyy-MM-dd) or a date-time with an offset, and the line number options take '.' as the decimal point (2.5), independent of the UI language; other text stops with exit code 2 before any request. Update and line files reject the DK Plus wire spellings (for example Text1, Project, Payment, Dimensions, and on lines Description2, LedgerCode, Discount, Dimentions) naming the request member, and the read-only members of a saved document or line (Amount, TaxAmount, Created, Modified, ...), instead of silently dropping them. An update with neither --file nor a field, or with a file that sets no member, stops with exit code 2 before any request; a Lines list counts only when a line sets a member other than Sequence. delete and lines delete require --yes; order delete and order lines delete take --purge; update and lines update need no --yes. Both update (the head PUT) and lines update (the line PUT) send only the supplied fields; whether DK Plus keeps or resets the unsent fields is unverified live, so try an update on a test company first. The doubled Swagger route that sales quote delete uses is also unverified live. v0.4.0: Breaking: customer create no longer has --contact-number, --contact-name, --contact-email or --contact-mobile, and a customer create or update --file with Contacts is rejected with exit code 2 naming customer contact create, because DK Plus ignores contacts in the customer document; the new customer contact list, get, create, update and delete commands manage contacts (create and update take direct options or a CustomerContactCreateRequest or sparse CustomerContactUpdateRequest --file; delete requires --yes; list uses the new customer.contact column profile). Breaking: customer create no longer has --receiver-number, --receiver-name, --receiver-email or --receiver-phone, a customer create or update --file with Receivers is rejected with exit code 2 naming customer receiver create, and one with Memos is rejected as read-only, because DK Plus ignores receivers and memos in the customer document (customer memos have no write endpoint); the new customer receiver list, get, create, update and delete commands manage item receivers (create and update take direct options or a CustomerReceiverCreateRequest or sparse CustomerReceiverUpdateRequest --file; delete requires --yes; list uses the new customer.receiver column profile). customer contact update and customer receiver update --file with a document that sets no member stop with exit code 2 before any request. Breaking: product and memo --file documents use the new nested request types; a nested QuantityInStock, QuantityOnBackOrders, QuantityPoOrders, QuantityOnHand, LastPurchased* or Modified key is rejected with exit code 2 naming the replacement instead of being sent, and ObjectDate is rejected as read-only in product, customer, vendor and work-request files. warehouse update-product --file now reads a ProductWarehouseSettingsRequest instead of the ProductWarehouse read model: stock quantities (including variation Quantity and QuantityOnBackOrders) are rejected naming inventory journal or count, Modified as read-only, and the earlier wire spellings LocationInWarehouse, DefaultPOQuantity, SkipPOSuggestion, Code2 and Description2 naming their replacements, all with exit code 2 before any request; it is an ordinary update and no longer takes --yes (passing --yes is now an unknown option). General-ledger account create and tax-group create --file now read GeneralLedgerAccountCreateRequest and GeneralLedgerTaxGroupCreateRequest instead of the read models: Modified is rejected as read-only, and the tax-group wire spellings Dim1, Dim2, Dim3, Reconciliate and InTaxType are rejected naming Dimension1, Dimension2, Dimension3, Reconcile and InputTaxType, with exit code 2 before any request. Unknown keys inside vendor Approvers, Dimensions, Expenses, Delivery, BankAccount and PaymentBankAccount are now forwarded to DK Plus instead of failing with exit code 2. JSON output includes ObjectDate, and Modified is no longer filled from it. ObjectDate is the dkPlus stored time (Stored Date) and the one DK Plus pages and filters on for those entities, otherwise Modified: the -m/--modified-since, --modified-after and --modified-before help says so, the default tables of customer, product, vendor, sales invoice, order, quote, recurring sale, project journal and work request show an ObjectDate column (customer transaction JSON output now includes ObjectDate too, and customer transaction list pages on it), and the customer, product, vendor and sales-document get tables add a Stored Date row. Numeric vendor transaction enum fields (all but JournalType) show their Swagger names instead of digits. Project work-entry updates no longer send an empty Properties object. Commands that take a page number and -n/--count now fail locally with exit code 2, before any request is sent, when page × count passes the DK Plus limit of 50,000 records per query, with a hint to narrow the query with a modified-after/modified-before window or another filter and start again from page 1. dimension list, project phase list, project task list and project journals continue past 50,000 records by re-anchoring a modified-after window on the entity's paging field (ObjectDate where the DK Plus list response has it, otherwise Modified); project work-request list-for, which has no modification filter, stops with exit code 2 before passing 50,000 records, as does any list whose window cannot advance safely. v0.3.1: fixes reads that failed on 0.3.0 because DK Plus returns enum fields as numbers (customer, product, employee, product category, vendor transaction and v2 project journal reads); numeric enum values now map to their members, and an unrecognized value reads as null with the raw value kept in AdditionalData. Text enum fields read a number as its Swagger spelling, so portable Project.Status and v2 order and quote Status read InProgress instead of digits (likewise employee Status, token Type, request-log ServiceType, customer transaction RecordType, product category Type, project transaction fields, v2 Origin and project journal Status); a numeric vendor-invoice ApprovedStatus now maps to its member, and an unknown company or permission enum value reads as null instead of failing the read. v0.3.0 (breaking): customer get --expand Options is now --expand Settings; customer JSON output is the flat DkPlusCustomer shape with enum member names and no options object; product update takes the item code as a positional argument; project request is now project work-request, whose list --type and --status take enum names; --file documents are the new CreateRequest and UpdateRequest types; every --file reader now fails on stderr with exit code 2 for an unknown key on a type without extension data, and for a key from the previous release, a renamed or read-only key, or an identity key in an update file, naming the replacement; vendor invoice and vendor transaction JSON keys follow the public names (id, dimension1, Unapproved); config columns selections that name a removed column (for example Options.VatExempt) stop with the existing update-or-reset message and the project.request profile is now project.work-request; a vendor invoice attachment without content reports a contract error; ordinary create and update commands still need no --yes. purchase invoice attachment without --output saves under the sanitized last segment of the server-supplied name in the current directory and never writes elsewhere; product --file documents with read-only keys such as Attachments, Changes or RecordId fail with exit code 2 instead of being silently dropped; employee list and get output (including --json) never contain payroll fields; sales order and quote Status, order DeliveryStatus and project Status in --file documents take enum member names. Earlier features remain: self-update, column selection, safe contract-mismatch errors, correlation IDs and the branded help. v0.4.2: on creates a blank --sales-person (or a blank SalesPerson in the file) counts as not given instead of being sent as an empty string; "sales order|quote|recurring lines create" refuse a line with only blank values; unquoted --line values are trimmed and "reference-line" is accepted as a key; a --number that already exists may update that document (unverified).