Innoslate Advanced Search: Quick Guide
A quick guide to searching your Innoslate project.
In the fast-paced world of model-based systems engineering (MBSE), quickly locating the right requirements, actions, risks, or diagrams across complex project databases can mean the difference between meeting deadlines and costly rework.
Innoslate’s Advanced Search feature empowers engineers, analysts, and project managers with a powerful, flexible query language to pinpoint entities with surgical precision. From simple keyword lookups to sophisticated attribute filtering, Boolean logic, and diagram-aware searches, this syntax transforms the Database View and search fields into a dynamic discovery tool—unlocking insights hidden in even the largest Innoslate projects.
Below is a quick guide reference for searching your project in Innoslate.
1. Common Field Qualifiers
| Qualifier | Description | Exact Example | Wildcard Example | Notes |
name: |
Matches entity names | name:"System Radar" |
name:Radar* |
Multi-word values must be enclosed in quotes. |
number: |
Matches entity numbers | number:5.1 |
number:5.* |
Exact search number:5.1 matches only 5.1 (no child levels like 5.1.1). |
description: |
Matches rendered text (description_text) |
description:"Fully verified" |
description:"*verified*" |
HTML markup is stripped; search against visible text. |
class: / type: |
Filter by schema class or type | class:Requirement |
class:Action* |
Limits results to the specified entity class. |
id: |
Matches internal entity integer ID | id:1042 |
— | Direct entity reference. |
globalid: |
Matches entity UUID | globalid:"a1b2c3..." |
— | Strict equality match. |
attributeid: |
Matches attribute definition ID | attributeid:5 |
— | Filters by custom schema attribute identifier. |
is:top |
Filters root-level hierarchy | is:top |
— | Returns top-level entities in current view. |
2. Boolean Logic
AND → both sides must match
Example: label:Risk AND class:Action
OR → either side matches
Example: label:System OR label:Subsystem
NOT → excludes the term
Example: NOT is:root
3. Attribute Search (by Type)
Correct Format: Class:"AttributeName [operator] Value"
Standardize format using Class:"Attribute=Value" or Class:"Attribute operator Value":
| Attribute Type | Supported Operators | Example Query | Matching Rules |
| TEXT / BIG_TEXT | = |
Class:"Vendor = Boeing*" |
Whole-value anchored; use * or % for partial/contains matching. |
| HTML / Description | = |
Class:"Rationale = *temperature*" |
Matches markup-stripped text column; HTML tags are excluded. |
| URI | = |
Class:"Link = [https://jira.org/](https://jira.org/)*" |
Anchored full URL match; use * for domain or path prefix matching. |
| GEOPOINT | =, >, <, >=, <= |
Location:"Latitude >= 38.8, Longitude <= -77.0" |
Numeric coordinate matching; Latitude = 20 does not match 20.3. Nulls evaluate as unset (not 0). |
| NUMBER / INTEGER | =, >, <, >=, <=, != |
Class:"Cost <= 50000" |
Numeric boundary comparisons. |
| DATE / DATETIME | =, >, <, >=, <= |
Class:"DueDate >= 2026-01-01" |
ISO-8601 formatted date evaluations. |
|
File Attachment |
= |
Artifact:"File=True" |
Does or does not have uploaded file to Artifact. |
4. Wildcards & Prefixes
Qualified searches are anchored to the entire field value. Use wildcards to expand matches:
| Symbol | Name | Description | Example Query | What It Matches |
* or % |
Suffix Wildcard (Prefix Match) | Matches strings beginning with the specified characters. | number:I.1* |
Matches I.1, I.1.1, and I.1.12. |
* or % |
Leading Wildcard (Suffix Match) | Matches strings ending with the specified characters. | number:*12 |
Matches I.1.12 and 12, but not I.1.123. |
* or % |
Surrounding Wildcards (Contains) | Matches strings containing the characters or phrase anywhere. | name:"*MBSE*" |
Matches any name containing MBSE. |
_ |
Single-Character Wildcard | Matches exactly one character (including letters, digits, spaces, and .). |
number:I.1.__ |
Matches I.1.12 (2 characters), but not I.1.1 or I.1.123. |
5. Special Filters
|
Qualifier |
Example |
Meaning |
|
is:root |
is:root |
Top-level (no parent) |
|
is:leaf |
is:leaf |
No Children |
|
is:orphan |
is:orphan |
No relationships |
|
is:diagram |
is:diagram |
Has generated diagram |
|
is:crossproject |
is:crossproject |
Cross Project Links |
|
diagram:Type |
Diagram:LML_ACTION |
Has Action Diagram |
|
relationship:”name”` |
relationship:"decomposed by" |
In decomposition |
6. Diagram Types (Short Names)
|
Short Code |
Full Name |
|
LML_ACTION |
Action Diagram |
|
SYSML_BDD |
Block Definition Diagram |
|
SYSML_IBD |
Internal Block Diagram |
|
LML_RISK |
Risk Diagram |
|
LML_TIMELINE |
Timeline Diagram |
|
UML_CLASS |
Class Diagram |
> Use: `diagram:"Action Diagram"` or `diagram:LML_ACTION’
> As of 4.14.2, can use like names like 'diagram:Action' instead of `diagram:LML_ACTION’
7. Sorting Results
Append order:<field> or order:<field> desc to sort search results:
| Sort Key | Description | Example |
order:name |
Sort alphabetically by Entity Name | class:Requirement order:name |
order:number |
Sort numerically/hierarchically by Entity Number | class:Action order:number |
order:created |
Sort by entity creation timestamp | order:created desc |
order:modified |
Sort by last entity edit timestamp | order:modified desc |
order:diagrammodified |
Sort by last diagram edit timestamp | class:Artifact order:diagrammodified desc |
order:related |
Sort by relationship update timestamp | order:related desc |