Skip to main content

DATA_Location

DATA_Location: TvxClientDataSet

Example​

procedure ScriptEvent(var Value: variant);
begin
  CreateData(DATA_Location, ['Code,string,100', 'Name,string,100', 'TypeNum,integer']);
  DATA_Location.Append;
  DATA_Location['Code'].AsString := 'LOCATION-001';
  DATA_Location['Name'].AsString := 'Example Location';
  DATA_Location['TypeNum'].AsInteger := 5;
  DATA_Location.Post;
  Value := DATA_Location.RecordCount;
end;

Usage​

DATA_Location provides the friendly dataset conventionally used for location Party master and partner-code mapping working data.

Conventional VxData context

Current helpers load Party master rows for party type 5. The separate Party_Location table maps partner-specific TheirCode values to a location PartyNum; it is a relationship row rather than the full location. Explicit SQL decides whether this object holds a Party, cross-reference or joined projection.

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

DATA_Branch is an exact alias of this object. A location record does not by itself prove inventory ownership, physical access or that it is valid for the current application/partner.

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_Location is the friendly dataset conventionally used while resolving or mapping a location party. 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_Location to TvxActionMan.FData12. Its diagnostic dataset name is DATA_Location.

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