I1226

// Generated display declaration:
I1226 = 1226

// Effective Pascal Script type and value:
const I1226: String = '1226';

// Current replacement: no named I1326 script constant exists
CurrentIssueNum := 1326;

Example

procedure ScriptEvent(var Value: variant);
var
  LegacyCode: string;
  CurrentIssueNum: integer;
begin
  LegacyCode := I1226;       // '1226'; retained for compatibility
  CurrentIssueNum := 1326; // current replacement has no named script constant
  Value := LegacyCode + ' -> ' + IntToStr(CurrentIssueNum);
end;

Usage

I1226 is a legacy script-visible String issue code with exact value '1226'.

• Do not use I1226 for new issue persistence on a current database.
• Audit older scripts that reference I1226; decide whether their intended current definition is 1326 and update the literal/type deliberately.
• Check the live Issue table before changing an upgraded customer system, because custom rows may differ from the governed fresh-build state.

Migration and compatibility boundary

Upgrade v1.12 added Issue 1226. Upgrade v1.17 later removes every Order and Shipment issue reference in the 1220–1229 range before deleting those Issue definitions. That migration is destructive for the affected historical issue rows; the documentation must not imply that those references are retained or automatically renumbered.

The v1.17 upgrade introduced replacement 1326; the current fresh-build table defines it with status 3/Issue.

The code gap is intentional. No I1326 member appears in the current Velox declarations, Velox scripting import or generated index. Where current logic requires the replacement, pass integer literal 1326 to an integer issue API, or string literal '1326' only when the receiving field explicitly requires text. Do not invent I1326 in script source.

Constant non-effects

Reading I1226:

• does not check quantity, price, pack-size or product state;
• does not look up either the deleted 1226 row or replacement 1326;
• does not translate 1226 to 1326;
• does not recreate deleted historical issue records; and
• does not call LogIssue, insert DIssue, change transaction status or navigate to /Administration/Product.

Additional Technical Info

I1226 is an exposed String constant with value '1226', historically used for Product not active. It is now a legacy/stale issue identifier: upgrade v1.17 deleted Issue definitions 1220–1229 and dependent Order/Shipment issue rows, then introduced the 1320–1329 replacement family.

The product still registers I1226, so a script can compile and read the digit text. The current fresh-build Table_Issue.sql does not create Issue 1226. Do not interpret script visibility as evidence that the matching database definition still exists.

Declaration, historical definition and current replacement

Property	Value/evidence
Script type/value	String / '1226'
Historical Issue 1226 description	Product not active
Historical status/route	3 (Issue) / /Administration/Product
v1.17 action	Delete Order/Shipment references and Issue rows 1220–1229
Current replacement number	1326
Current replacement description	Product not active
Current fresh-build replacement status	3 — Status_Issue
Current replacement route	/Administration/Product
Named I1326 script constant	Not registered

Runtime risk of using the legacy value

GetIssueLevel queries the live row. On a current fresh-build database, GetIssueLevel(1226) finds no row and returns fallback 6 (Error). That fallback is not a recreated Issue definition and must not be used to conclude that 1226 is safe to persist.

An issue-persistence path that stores an Issue number under a foreign key can fail when 1226 is absent. Other paths may log text before a later insert fails or may behave differently according to their transaction and rollback boundaries. Verify the chosen API and live schema; replacing 1226 with 1326 is an intentional migration decision, not a cosmetic string change.

Issue API behavior

The reusable Scriptlet's local CreateIssue always calls LogIssue and optionally inserts its supplied number and description into DIssue; it does not call GetIssueLevel. The separate InvoiceIssue lifecycle queries configured severity, queues data, and later persists issue rows with status and notification effects. Neither API silently maps 1226 to 1326.

Related entries

• GetIssueLevel explains why a missing row returns 6 without creating it.
• InvoiceIssue documents one persistence lifecycle and its rollback/queue quirks.
• Status_Issue is the current fresh-build status for replacement 1326.

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

Created 2026-07-15