I1739

// Generated display:
I1739 = 1739

// Effective script type/value:
const I1739: String = '1739';

Example

procedure ScriptEvent(var Value: variant);
var
  IssueCode: string;
  IssueNum: integer;
begin
  IssueCode := I1739;               // '1739'
  IssueNum := StrToInt(IssueCode); // integer issue APIs need 1739
  Value := IssueCode + ':' + IntToStr(IssueNum);
end;

Usage

I1739 is the script-visible String code '1739' for Issue 1739 (Contact Code Not Specified).

• Test the exact source field under an explicit blank/null policy before selecting I1739.
• Use the String for text; use 1739 or explicit conversion for integer APIs.
• Include field name, source record, application/partner scope and expected code namespace in the detail.

Exact diagnostic meaning

Code Not Specified means no identifying Contact code was supplied for the operation. It is distinct from:

• Missing Required Value, which can refer to any required field;
• Not Found, where a code/key was supplied but resolution failed; and
• Invalid Value, where a supplied value exists but violates its rule.

Choose this code only after applying the map's defined null/blank/whitespace policy. The constant itself does not decide whether Null, Unassigned, Empty, '' or whitespace counts as unspecified.

The fresh-build route /Administration/Contact is an operator-navigation hint; it does not prove a matching record exists or identify the failed input.

Non-effects and persistence

I1739 does not validate, default or trim the code; it does not perform a lookup, create Contact data, call LogIssue, insert DIssue, update transaction status or navigate to administration.

The reusable Scriptlet's local CreateIssue logs and optionally inserts its supplied issue without querying severity. InvoiceIssue uses live severity and deferred persistence. Their side effects belong to those APIs, not to this constant.

Additional Technical Info

I1739 is the script-visible String constant '1739' for the VxData Issue definition Contact Code Not Specified. It identifies the specific absence of a Contact business code; reading the constant does not inspect input, test blankness, look up master data or create an issue.

Native source and the Pascal Script import provide digit text. The generated index omits the quotes. The example was source-reviewed and not executed against VxData.

Declaration and definition

Property	Fresh-build/source value
Script type/value	String / '1739'
Integer Issue number	1739
Description	Contact Code Not Specified
Issue.Status	0 — Status_NotSet
AdminUrl	/Administration/Contact

String/integer and severity boundaries

Integer issue APIs require 1739 or explicit StrToInt(I1739); do not rely on implicit coercion. GetIssueLevel reads the live row and returns fallback 6/Error if it is absent.

Fresh-build and v1.15 sources both configure level 0/Not Set. That is lower than Success in numeric aggregation and is not automatically equivalent to Error despite the diagnostic wording. A customised live row can differ. Calling code must define whether missing Contact code stops, warns, defaults or continues processing.

Related entries

• GetIssueLevel documents live severity and absent-row fallback.
• InvoiceIssue documents one deferred issue lifecycle.
• Status_NotSet is the fresh-build status value 0.

No Delphi or Free Pascal equivalent exists; this is a Velox-owned identifier.

Created 2026-07-15