Type_Customer
Type_Customer = 1
Example
procedure ScriptEvent(var Value: variant);
begin
Value := GetPartyTypeCode(Type_Customer); // 'Customer'
end;
Usage
Type_Customer identifies the preferred Customer party role as Party_Type.Num value 1 for Velox scripts and mappings.
Value
| Property | Value |
|---|---|
| Script type | LongInt |
| Numeric value | 1 |
| Paired text | Type_Customer_String = Customer |
| Deprecated numeric alias | Party_Customer = 1 |
| Database domain | Party_Type.Num; Party.TypeNum |
| Reference-table helper result | Party_Customer |
| Issue helper result | 1014 |
Additional Technical Info
Type_Customer is the preferred script-visible LongInt identifier for the Customer party role. Its fixed value is 1, paired with Type_Customer_String.
It identifies a party-role domain value. It does not find or create a party, add a Party_Customer reference row, validate a relationship or grant access to party data.
Implementation
Velox declares and registers fixed value 1. GetPartyTypeCode maps it to Customer; GetPartyTypeNum performs the reverse mapping. The preferred numeric name is in the tag map, so <!Type_Customer!> expands to 1.
Fresh-build VxData seeds Party_Type row 1 as Customer, and Party.TypeNum references that domain. The role-specific reference table is Party_Customer.
GetReferenceTableForPartyType returns fixed text Party_Customer. GetIssueForPartyType returns integer 1014. Their case statements use the numerically identical deprecated Party_Customer 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_Customerand deprecatedParty_Customerare numerically indistinguishable after evaluation. Use the preferredType_*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
1, notCustomer. GetIssueForPartyTypereturns an integer, whereas exposedIxxxxissue-code constants are strings. Check the receiving API before substituting representations.- Unsupported role numbers make the table helper return
Unknownand the issue helper return generic fallback1029.
Side effects
Reading Type_Customer, 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
Type_Customer_Stringis the paired canonical role text.Party_Customeris the deprecated numeric alias.GetPartyTypeCodeconverts a supported role number to text.GetPartyTypeNumconverts recognised role text to a number.GetReferenceTableForPartyTypeandGetIssueForPartyTypeexpose fixed role metadata.