Skip to main content

DATA_OrderLineBatch

DATA_OrderLineBatch: TvxClientDataSet

Example​

procedure ScriptEvent(var Value: variant);
begin
  CreateData(DATA_OrderLineBatch, ['OrderLineNum,integer', 'BatchCode,string,50', 'BatchExpiry,date', 'Qty,double']);
  DATA_OrderLineBatch.Append;
  DATA_OrderLineBatch['OrderLineNum'].AsInteger := 1001;
  DATA_OrderLineBatch['BatchCode'].AsString := 'BATCH-001';
  DATA_OrderLineBatch['BatchExpiry'].AsDateTime := EncodeDate(2027, 12, 31);
  DATA_OrderLineBatch['Qty'].AsFloat := 2;
  DATA_OrderLineBatch.Post;
  Value := DATA_OrderLineBatch.RecordCount;
end;

Usage​

DATA_OrderLineBatch provides the friendly dataset conventionally used for order-line batch allocation working data.

Conventional VxData context

The current Order_Line_Batch table requires OrderLineNum and records batch code, expiry, quantity, revision/status, hash and audit fields. This client object does not automatically follow the current DATA_OrderLine record or enforce that foreign key.

That convention is guidance for choosing queries and field names, not a guarantee. A configured source/destination or customer extension may expose a different subset or additional columns. Use FindField for optional columns and never assume a named field merely because this page describes the current base schema.

Behaviour, lifecycle and side effects

  • Velox loads all returned rows into memory and preserves fetched string whitespace. Large results can use substantial memory.
  • Field access, navigation, filtering, indexing, inserts, edits, posts and deletes mutate this shared object. Closing or recreating it invalidates retained fields and record positions.
  • Post updates the client dataset; it is not proof of an external database write or transaction commit. SQL or file effects belong to the function used to populate or persist it.
  • Data helper functions generally catch and log SQL or creation failures, potentially leaving the object inactive or reset. Direct invalid field, conversion or dataset-state operations can raise.
  • Action cleanup closes every friendly dataset. Velox owns the object; never free it or depend on records surviving another action execution.
  • The mutable dataset and cursor are not thread-safe. Do not hand the reference to asynchronous work or let nested code reposition it without an explicit contract.

Alias and naming cautions

Batch codes can repeat across products, owners or locations. Preserve the line/product context and treat expiry as a date value under the flow's explicit date policy.

The friendly suffix never validates record type, authenticates a party or application, enforces foreign keys or prevents the dataset being reused for unrelated data.

Additional Technical Info​

DATA_OrderLineBatch is the friendly dataset conventionally used for batch allocations belonging to order lines. It is a live TvxClientDataSet reference; its name does not load data, choose a connection, execute SQL or impose a field layout.

Runtime binding and identity

Velox constructs the object with the action and binds DATA_OrderLineBatch to TvxActionMan.FData27. Its diagnostic dataset name is DATA_OrderLineBatch.

The dataset begins inactive and without fields. CreateData, the Data query helpers and load methods can each replace its current schema and records. Every script using this action sees the same live cursor, filters, indexes and edits until the dataset is closed or repopulated.

Related entries

External references

Created 2026-07-15