String

In Revit, a string is simply a piece of text stored in a parameter. It could be anything from a door number like "D-101", a material name like "Concrete", or a status field like "Approved". Unlike numbers or true/false values, strings are made up of letters, numbers, and symbols — and are treated as text, even if they contain digits. You’ll often see string parameters in fields like Type Name, Mark, Comments, or Manufacturer. They’re essential for labeling, organizing, and tagging elements in a model — and for ensuring clean, consistent data when exporting or creating schedules.

✅ Validator: String: Equal

Description: Passes only if the string value exactly matches the specified value (case-sensitive unless configured otherwise).

🔧 Revit Example:

• Parameter: Fire Rating Description of a Wall Type
• Rule: Fire Rating Description = '60 minutes'

📌 Use Case:

Ensures that text-based parameters follow exact wording, which is critical when automating schedules, tags, or exports. Prevents mismatches due to inconsistent capitalization or phrasing.

✅ Validator: String: Not Equal

Description: Passes only if the string value does not exactly match the specified value.

🔧 Revit Example:

• Parameter: Status of a Room
• Rule: Status ≠ 'Undefined'

📌 Use Case:

Flags rooms that still have a default or placeholder status, helping to ensure that all spaces are correctly classified (e.g., 'Occupied', 'Vacant', 'Under Construction') before issue or export.

✅ Validator: String: Contains

Description: Passes if the string contains a specified substring.

🔧 Revit Example:

• Parameter: Comments of a Wall Instance
• Rule: Must contain 'firestop'

📌 Use Case:

Checks that key terms like firestop, acoustic seal, or structural support are included in comments for tracking special installation requirements. Useful for coordination between trades or documentation quality control.

✅ Validator: String: Not Contains

Description: Passes only if the string does not contain the specified substring.

🔧 Revit Example:

• Parameter: Type Name of a Duct Fitting
• Rule: Must not contain 'Copy'

📌 Use Case:

Prevents the use of duplicated or lazily named families that include "Copy" in their type name, improving model clarity and avoiding confusion during scheduling or quantity takeoff.

✅ Validator: String: Part Of

Description: Passes if the string value exists as an element within a predefined list of allowed values.

🔧 Revit Example:

• Parameter: Material Code of a Wall Finish
• Rule: Must be part of ['MAT-001', 'MAT-002', 'MAT-003']

📌 Use Case:

Ensures that the material codes used in the model are approved entries from a controlled list, helping standardize data for export, cost estimation, or facility management.

✅ Validator: String: Not Part Of

Description: Passes only if the string value is not found in a predefined list of disallowed values.

🔧 Revit Example:

• Parameter: Finish Code of a Floor Type
• Rule: Must not be part of ['TBD', 'N/A', 'Unknown']

📌 Use Case:

Helps catch incomplete or placeholder values that should be resolved before construction documentation or handover. Keeps data clean and export-ready.

✅ Validator: String: Empty

Description: Passes only if the string value is empty (i.e. no text at all).

🔧 Revit Example:

• Parameter: Notes on a Drafting View
• Rule: Must be empty

📌 Use Case:

Ensures that notes fields are intentionally left blank in views where no annotations should appear — useful for templates or clean deliverables where leftover text could cause confusion.

✅ Validator: String: Not Empty

Description: Passes only if the string value is not empty (i.e. contains some text).

🔧 Revit Example:

• Parameter: Door Number of a Door Instance
• Rule: Must not be empty

📌 Use Case:

Ensures that all doors are properly numbered, which is essential for scheduling, tagging, and wayfinding. Prevents missing data in plans and specifications.

✅ Validator: String: Matches

Description: Passes if the string value matches a specified regular expression pattern.

🔧 Revit Example:

• Parameter: Door Number of a Door Instance
• Rule: Must match the pattern ^D-[0-9]{3}$ (e.g., "D-101")

📌 Use Case:

Enforces a consistent naming convention for doors — such as prefix plus 3-digit number — which is critical for automation, schedules, and coordination with external systems like FM or asset databases.