Skip to main content
Share / Export

Setting Up UD User Validation

UD User Validation creates stored validation procedures that attach to any non-validated field (standard or custom). Parameters compare input to a table column or a value. After compile, assign them on Field Properties / F3 → System Overrides → Validation. Form help: About the UD User Validation Form. Procedure: Create a Validation Procedure. Hub: Custom Validation Procedures. There is no help slug setting-up-ud-user-validation.

Before you start​

  • Access to UD User Validation.
  • Target field is not already validated.
  • Know the validating table(s) and columns. For other configurations Trimble says speak to your system administrator.

Steps — create​

  1. Open UD User Validation → Info tab → New Record.
  2. Validation Procedure: up to 27 characters, no spaces. After tab-off Vista prefixes usp (example CompanyVehicles → uspCompanyVehicles).
  3. Description: up to 30 characters.
  4. Tables tab: add validating table(s) (F4). Job example is usually JCJM (JC Jobs). About-page sample grids sometimes show JCCM for Active = Y — treat JCJM as the job master unless your design is company-level.
  5. Per table: Error Message (up to 255; examples “Not a valid Job” or “Job not set up in JC Jobs (JCJM)”).
  6. Description Column: column shown as a label after a valid entry (F4). Job example: JCJM Description. Employee example: SortName next to the number.
  7. Parameters tab: And/Or, Type (Left), Parameter/Column Name, Operator (= < > <= >= <>), Type (Right), ColumnName, Value.
    • Typical: Left = Parameter, Right = Column (placeholder in Parameter/Column Name is replaced at assignment with the field’s Field Seq#).
    • Or Left = Column, Right = Value (Y/N, On/Off, flags; open-job example uses Value 1).
    • ColumnName / Value enable only when Right is Column or Value.
    • First sequence usually has no And/Or. Parentheses group conditions; a closing ) may be added at compile.
    • Parameters may use only tables/columns already on the Tables tab.
    • Not* And/Or operators are listed but “not currently available.”
  8. SQL tab → Initialize (shows SQL). Re-Initialize wipes later SQL edits.
  9. Compile (creates the SQL procedure). Illegal commands fail compile (alter, create, delete, drop, exec, insert, update, truncate, sp_, xp_, and similar).
  10. Save.
  11. Assign (below).

Steps — assign (F3 → System Overrides → Validation)​

  1. Open the field’s Form/Field Properties (F3).
  2. Optionally require a value.
  3. Set Level (options in F1 help). If level is blank or “Warning, allow save,” an invalid entry’s error message can appear in the Description field.
  4. Procedure (F4 = custom procedures).
  5. Parameters: usually the field’s Field Seq# so form input maps to the procedure parameter.
  6. Apply. Optional: Show In Grid + Description in Grid = 1-Show Above Grid Only (description above the grid, never inside it).

Hard rules​

  • No spaces in the procedure name; stored name is usp + name.
  • Re-Initialize deletes manual SQL changes.
  • Only Tables-tab tables/columns in parameters.
  • About vs Create disagree on job table (JCCM vs JCJM) and on whether Create step 5’s F4 refers to step 2 or step 3 (table is step 3).
  • Create says “see Assigning a Validation Procedure section below,” but assignment is a separate topic.

Notes​

  • Related: Create a Validation Procedure; Assign a Validation Procedure; Customizing Validation using the System Overrides tab; Field Properties / F3.