Skip to main content

Type_Location

Type_Location = 5

Example​

procedure ScriptEvent(var Value: variant);
begin
  Value := GetPartyTypeCode(Type_Location); // 'Location'
end;

Usage​

Type_Location identifies the preferred Location party role as Party_Type.Num value 5 for Velox scripts and mappings.

Value

PropertyValue
Script typeLongInt
Numeric value5
Paired textType_Location_String = Location
Deprecated numeric aliasParty_Location = 5
Database domainParty_Type.Num; Party.TypeNum
Reference-table helper resultParty_Location
Issue helper result1018

Additional Technical Info​

Type_Location is the preferred script-visible LongInt identifier for the Location party role. Its fixed value is 5, paired with Type_Location_String.

It identifies a party-role domain value. It does not find or create a party, add a Party_Location reference row, validate a relationship or grant access to party data. The Location role also participates in location-specific product quantity and operational relationships; this identifier does not decide which relationship a workflow requires.

Implementation

Velox declares and registers fixed value 5. GetPartyTypeCode maps it to Location; GetPartyTypeNum performs the reverse mapping. The preferred numeric name is in the tag map, so <!Type_Location!> expands to 5.

Fresh-build VxData seeds Party_Type row 5 as Location, and Party.TypeNum references that domain. The role-specific reference table is Party_Location.

GetReferenceTableForPartyType returns fixed text Party_Location. GetIssueForPartyType returns integer 1018. Their case statements use the numerically identical deprecated Party_Location label, so this preferred value selects the same branch.

Behaviour

Text-to-number conversion is case-insensitive but non-trimming; unsupported text returns Null. Number-to-text conversion returns Null for a Null or unsupported number.

The reference-table helper returns a name only and does not open a table or dataset. The issue helper returns a number only and does not create, log or persist an issue.

Edge cases and quirks

  • Type_Location and deprecated Party_Location are numerically indistinguishable after evaluation. Use the preferred Type_* name in new or revised scripts.
  • Current helpers retain deprecated Party_* labels internally. This does not make the preferred identifier unsupported; the equal integer selects the branch.
  • Party-role values overlap many unrelated numeric families; PascalScript does not retain the role domain.
  • Text conversion accepts case differences but not leading/trailing whitespace.
  • Both preferred and deprecated numeric names are tag entries; this tag expands to 5, not Location.
  • GetIssueForPartyType returns an integer, whereas exposed Ixxxx issue-code constants are strings. Check the receiving API before substituting representations.
  • Unsupported role numbers make the table helper return Unknown and the issue helper return generic fallback 1029.

Side effects

Reading Type_Location, comparing it, expanding its tag or using the converters/helpers has no database or state-changing side effect.

Errors

Reading the constant does not raise an error. Converter misses return Null; helpers use their documented fallbacks. Persisting a role not present in Party_Type can fail a foreign key.

Performance and concurrency

This is immutable compiled metadata. Access and fixed-case conversion/helper lookup are constant-time for practical purposes and carry no shared mutable party state.

Remarks

The example is source-reviewed and non-destructive. A returned table name is metadata, not SQL authorisation or proof that a matching row exists.

Related entries

Created 2026-07-15