Skip to content
  • There are no suggestions because the search field is empty.

Advanced Search for Entities

Perform searches for specific entities within your project’s database via the ‘Search’ feature in Innoslate.

database view snapshot

Innoslate provides the ability to perform searches for specific entities within your project’s database via the ‘Search’ feature.

You will find the ‘Search’ field used to enter your search criteria at the top center of the toolbar in ‘Database View.’

You can search based on a number, a word or group of words, a label, a class, or both class and label in any combination you wish. Simply type your search criteria in the search box and hit ‘Enter’ on your keyboard or click the magnifying glass button to the right of your entered text to display your search results.

Please note, this article is applicable for all versions of Innoslate 4.

Basic Searches

  • By Number
    Searching for a number checks the number, name, and description of every entity in your database looking for your search criteria.

    For example:
    2.3.2.0 – Matches entities that contain the number 2.3.2.0.
  • By Word(s)
    Searching for a word or group of words checks the number, name, and description of every entity in your database looking for your search criteria.

    For example:
    Stakeholder – Matches entities that contain the word stakeholder.
    OR
    preliminary design – Matches entities that contain the word preliminary and the word design.

Basic Searches with Qualifiers

  • Label
    You can narrow your search results by labels, using the label qualifier.  Since entities can have multiple labels you can also use multiple of these qualifiers.
     
    For example:
    planning label:Activity – Matches entities with the word planning that are also labeled as an Activity.
    OR
    label:Activity label:Process – Matches entities with both the Activity and Process labels.
  • Class
    You can narrow your search results by class, using the class qualifier. Combine this with a label qualifier to further refine results.

    For example:
    mitigate risk class:Action – Matches entities with the word mitigate and the word risk that are of the schema-based class Action.
    OR
    power class:Requirement label:“Functional Requirement” – Matches entities with the word power that are of the schema-based class Requirement and also labeled as a Functional Requirement.

Advanced Searches

  • AND and OR
    When a more advanced search is required, it is possible to use the AND and OR search modifiers for more precise and refined results.  The AND modifier requires both values on either side of the AND to be found. The OR modifier requires only one (1) of the values on either side of the OR to be found.  These modifiers can also be used in combination with a single word, class qualifier, and/or label qualifier.

    For example:
    label:Facility AND label:Infrastructure – Matches entities that are labeled with both the Facility and Infrastructure labels.
    OR
    distribution label:System OR label:Subsystem – Matches entities with the word distribution that are also labeled either as a System or a Subsystem.
  • NOT
    The NOT modifier will find the inverse of the following search term.

    For example:
    NOT is:root – Matches entities that are not roots in hierarchies.
    OR
    NOT refined class:Action – Matches entities that do not have the word ‘refined’ and are of the schema-based class Action.
  • Wildcards
    Innoslate supports both multi-character and single-character wildcards across search queries and qualified attribute filters:
  • Multi-Character Wildcard (% or *): Matches zero or more arbitrary characters.
    • number:I.1% or number:I.1* matches I.1, I.1.1, and I.1.12.
    • Name:%MB% or Name:*MB* matches any entity containing MB anywhere in its name.
  • Single-Character Wildcard (_): Matches exactly one character (including periods, letters, digits, or spaces).
    • Name:Co_t matches Cost or Coat.
    • number:I.1.__ matches I.1.12 (two characters after the period), but does not match I.1.1 or I.1.123.
    • number:I.1._ matches I.1.1 (one character after the period), but does not match I.1.12.
    • number:I_1* matches I.1.12 because _ matches the period delimiter ..
  • Prefix
    Innoslate supports the asterisk (*) wildcard to match variable characters across entity values. In qualified attribute searches (such as number:, name:, and description:), search terms are anchored to the entire field value rather than automatically treated as a "contains" match.
    Use * to specify whether you are matching a prefix, suffix, or substring:

    For example:
  • Suffix Wildcard / Prefix Match (text*): Matches any string starting with the specified characters.
    • number:I.1* matches I.1, I.1.1, and I.1.12. It does not match 2.I.1.
    • number:5.* matches 5.1, 5.2, and 5.1.12.
  • Leading Wildcard / Suffix Match (*text): Matches any string ending with the specified characters.
    • number:*12 matches I.1.12 and 12, but does not match I.1.123.
  • Surrounding Wildcards / Substring Match (*text*): Matches the characters anywhere inside the field value.
    • number:*I.1* matches I.1, I.1.12, or Section I.1.A.
    • name:*MBSE* matches any entity whose name contains "MBSE" anywhere in the title.
  • Stop Words
    How stop words (common terms like is, the, a, and) behave depends on whether you run an unqualified global search or a qualified field search.
  • Syntax & Rules

    • Qualified Attribute Searches (name:, number:, description:):
      • Execute as direct column evaluations and bypass stop-word filtering entirely.
      • Terms are anchored to the full field value. An exact search for Name:is evaluates whether the name strictly equals "is". It does not match an entity named "Innoslate is a MBSE tool".
      • To find stop words embedded in full text, wrap them in wildcards: Name:"*%is%*" or Description:"* is *".
    • Unqualified Global Searches:
      • Queries entered without a field qualifier (e.g., searching is or Innoslate is a MBSE tool in the main search bar) query the full-text search index across name, number, and description.
      • Full-text indexing retains matches across all populated fields.

    Examples

    • Single Stop Word in Qualified Search:
      • Query: Name:is
      • Result: Not found (unless the entity's name consists solely of the word "is").
      • Query: Name:"%is%"
      • Result: Found for entities like "Innoslate is a MBSE tool" or "This is an Asset".
    • Stop Word in Unqualified Search:
      • Query: is
      • Result: Found. Matches any entity where "is" appears across name, number, or description.
    • Multi-Word Phrase with Stop Words:
      • Query: Description:"Innoslate is a MBSE tool"
      • Result: Found (matches the entire description exactly).
      • Query: Description:Innoslate
      • Result: Not found (must use Description:"*Innoslate*" because the field is anchored to the full string).

    Database Engine Summary (PostgreSQL 18 vs. SQL Server 2022)

    Query Type Syntax Example PostgreSQL 18 SQL Server 2022
    Exact Qualified Name:Innoslate Immediate (Exact match) Immediate (Exact match)
    Wildcard Qualified Name:Inn* or Name:%Inn% Immediate Immediate
    Anchored Description Description:"*MBSE*" Immediate (reads description_text) Immediate (reads description_text)
    GEOPOINT Numeric Latitude >= 20 Immediate (ignores nulls) Immediate (ignores nulls)
    Unqualified Global Full-Text Innoslate is a MBSE tool Immediate Available after asynchronous crawl completes

Attribute Search

Attribute searches allow you to search for attributes contained in entities. Innoslate supports the >, <, >=, <=, or = characters to search for attributes or attributes in ranges. The list below outlines the searches that can be performed on each attribute type. Attribute type can be found under the Type column in class or relation in the schema. Classes and Attributes names are case sensitive, whereas the values are not. Classes with spaces are pascal cased to perform the search by class with attributes.

  • TEXT: Used for short custom fields such as "Vendor", "Component Type", or "Status Code".
    Operators Supported: =

    For example:

    • Exact Match (=):
      • Query: Vendor="Lockheed Martin"
      • Matches: An entity where the Vendor attribute is strictly "Lockheed Martin".
      • Does Not Match: "Lockheed Martin Aeronautics" or "Vendor: Lockheed Martin".
    • Starts With / Prefix (* or %):
      • Query: Vendor="Lockheed*"
      • Matches: "Lockheed", "Lockheed Martin", "Lockheed Martin Space".
    • Contains / Substring (*text* or %text%):
      • Query: Status="*Approved*"
      • Matches: "Approved", "Pre-Approved", "Approved by Lead".
    • Single-Character Wildcard (_):
      • Query: PartNumber="PN-10_4"
      • Matches: "PN-1014", "PN-10A4".
      • Does Not Match: "PN-10114".
  • NUMBER: Matches entities whose number exactly equals the specified value.
    Operators Supported: >, <, >=, <=, =

    For example:
    number:I.1 returns only the entity numbered I.1. It no longer returns hierarchical child numbers such as I.1.1 or I.1.12. To search across a branch or include sub-entities, use wildcard syntax (e.g., number:I.1* or number:5.*).

  • BIG_TEXT:Used for long notes, rationale, multiline comments, or raw logs without markup.
    Operators Supported: =

    For example:

    • Exact Match (=):
      • Query: Rationale="Operational requirement verified by test run 4."
      • Matches: Only entities where the entire field content is that exact sentence and nothing else.
    • Contains Keyword / Phrase:
      • Query: Rationale="*flight test*"
      • Matches: Entities where "flight test" appears anywhere within a multi-paragraph rationale.
    • Ends With (* at the start):
      • Query: ReviewComments="*pending final signoff"
      • Matches: Any comments block terminating with "pending final signoff".
    • Multi-Word Exact Match inside Text:
      • Query: Notes:"*high temperature limit*"
      • Matches: Notes containing that exact three-word phrase in sequence.
  • HTML: Searches against HTML attributes target the normalized, markup-stripped text column (description_text). You cannot query raw HTML markup tags like <div>, <p>, or <b>.
    Operators Supported: =

    For example:

    • Exact Match (=):
      • Query: Description:"System shall shut down automatically."
      • Matches: An entity whose rendered text is exactly "System shall shut down automatically." (even if stored internally as <p>System shall shut down automatically.</p>).
      • Does Not Match: If the description has a second sentence or additional text.
    • Contains / Substring (* or %):
      • Query: Description:"*cooling subsystem*"
      • Matches: Any entity whose rich-text description mentions "cooling subsystem" anywhere in the body.
    • HTML Markup Exclusion Example:
      • Query: Description:"*<b>CRITICAL</b>*"
      • Does Not Match: Will return no results because tags (<b>, </b>) are stripped prior to indexing. Use Description:"*CRITICAL*" instead.
  • ENUMERATION: Matches entities in a class with the attribute that contains the enumeration text.
    Operators Supported: =

    For example:
    Requirement:“Status=Draft” – Matches entities in Requirement class that have the attributes Status that contain the value Draft. 

  • PERCENT: Matches entities in a class with the attribute that evaluates as true.
    Operators Supported: >, <, >=, <=, =

    For example:
    Action:“Percent Complete>75” – Matches entities in Action class that have the attributes Percent Complete that is greater than 75. 

  • DATETIME: Matches entities in a class with the attribute that evaluates as true. DateTime accepts 12 different DateTime formats. These formats can be seen in the list below. Time is standard to military time so 12 am is 00 and 12 pm is 12.

    Important: Entities with attributes of datetime created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the DateTime attribute.

    Operators Supported: >, <, >=, <=, =
    DateTime Supported Formats:
    yyyy-MM-dd HH:mm:ss
    yyyy-MM-dd HH:mm
    yyyy-MM-dd
    MM-dd-yyyy HH:mm:ss
    MM-dd-yyyy HH:mm
    MM-dd-yyyy
    yyyy/MM/dd HH:mm:ss
    yyyy/MM/dd HH:mm
    yyyy/MM/dd
    MM/dd/yyyy HH:mm:ss
    MM/dd/yyyy HH:mm
    MM/dd/yyyy

    For example:
    Action:“Start<2020-12-25 13:45:30” – Matches entities in Action class that have the attributes Start that is less than 1:45.30 pm on December 25, 2020. 

  • URI: Used for external references, Jira issue links, Git commits, or documentation URLs.
    Operators Supported: =

    For example:

    • Exact Match (=):
      • Query: ReferenceURI="[https://github.com/org/repo/issues/104](https://github.com/org/repo/issues/104)"
      • Matches: Entities pointing strictly to issue #104.
    • Domain / Path Prefix Match:
      • Query: ReferenceURI="[https://jira.company.com/](https://jira.company.com/)*"
      • Matches: Any entity linked to an issue or ticket hosted under [https://jira.company.com/](https://jira.company.com/).
    • Identifier Substring Match:
      • Query: SpecificationLink="*SPEC-4012*"
      • Matches: URLs containing that specification ID anywhere in the path or query parameters (e.g., [https://specs.internal/view?doc=SPEC-4012&rev=2](https://specs.internal/view?doc=SPEC-4012&rev=2)).
  • FILE: Matches entities in a class with the attribute that contains a file attachment.
    Operators Supported: =

    For example:
    Artifact:“File=True” – Matches entities in Artifact class that have the attribute File that contains a file attachment.
    OR
    Artifact:“File=Yes” – Matches entities in Artifact class that have the attribute File that contains a file attachment.

  • DURATION: Matches entities in a class with the attribute that evaluates as true.
    Operators Supported: >, <, >=, <=, =

    Important: Entities with attributes of duration created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the duration attribute.

    For example:
    Action:“Duration>=1.5 Hours” – Matches entities in Action class that have the attributes Duration that is greater than or equal to 1.5 hours. 

  • GEOPOINT: GEOPOINT attributes store geographic positions (Latitude, Longitude, and optionally Altitude). They evaluate numerically rather than through partial text matching.
    Operators Supported: >, <, >=, <=, =

    For example:

    • Exact Coordinate Match (=):
      • Query: Location:"Latitude = 38.8977, Longitude = -77.0365"
      • Matches: Entities located precisely at those coordinates.
      • Does Not Match: An entity with Latitude: 38.89771 or Latitude: 38.
    • Single-Axis Exact Match:
      • Query: SiteCoordinates:"Latitude = 20"
      • Matches: Entities with a latitude of exactly 20.0.
      • Does Not Match: 20.3, 20.001, or unset/null coordinates.
    • Bounding Range / Regional Search (>, <, >=, <=):
      • Query: AssetLocation:"Latitude >= 30, Latitude <= 45, Longitude >= -120, Longitude <= -70"
      • Matches: Any entity positioned within the specified geographic bounding box.
    • Altitude Filtering:
      • Query: Waypoint:"Altitude > 10000"
      • Matches: Waypoints recorded with an altitude strictly greater than 10,000 meters/feet.
      • Does Not Match: Entities where altitude was left blank or null (will not default to 0).
  • QUALITY: Matches entities in a class with the attribute that contains the value Yes or No, or True or False.
    Operators Supported: =

    For example:
    Requirement:“Clear=True” – Matches entities in Requirement class that have the attribute Clear that contains the value of Yes.
    OR
    Requirement:“Clear=Yes” – Matches entities in Requirement class that have the attribute Clear that contains the value of Yes.

  • MULTIPLICITY: Matches entities in a class with the attribute that contains the string of text.
    Operators Supported: =

    For example:
    Vehicle:“Wheels=2..4” – Matches entities in Vehicle class that have the attributes Wheels that contain the value 2..4. 

  • USER_TEAM: Matches entities in a class with the attribute that contains the string of users or teams.
    Operators Supported: =

    Important: Entities with attributes of user_team created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the user_team attribute.

    For example:
    Issue:“Assignee=support” – Matches entities in Issue class that have the attribute Assignee that contains the user support.

  • MULTISELECT: Matches entities in a class with the attribute that contains the enumeration text.
    Operators Supported: =

    Important: Entities with attributes of multiselect created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can bed any change to the entity and not necessary to the multiselect attribute.

    For example:
    Flag:“Color=green” – Matches entities in Color class that have the attributes Color that contain the values green.

Diagram Search Names

In version 4.14.2, database queries using 'diagram:' support the below additional diagram aliases. You can use thenames in Diagrams Type or Supported Diagram Names listed below and it will highlight the Diagram filter on the left sidebar of database view:

Diagrams Type

Supported Diagram Names

A0_DIAGRAM

icom, icom diagram

IDEF0_DIAGRAM

idef0, idef0 diagram

LAYER

layer, layer diagram

LML_ACTION

action, action diagram

LML_ASSET

asset, asset diagram

LML_HIERARCHY

hierarchy, hierarchy chart, hierarchy diagram

LML_I2

i2, i2 diagram, i-squared, i-squared diagram

LML_ICD

icd, interface control, interface control diagram

LML_N2

n2, n2 diagram, n-squared, n-squared diagram

LML_PHYSICAL_INPUT_OUTPUT_DIAGRAM

physical, physical diagram, physical i/o, physical i/o diagram

LML_RISK

risk, risk diagram

LML_SPIDER_DIAGRAM

spider, spider diagram

LML_TIMELINE

timeline, timeline diagram

RADAR_DIAGRAM

radar, radar diagram

SYSML_ACTIVITY

activity, activity diagram

SYSML_BDD

bdd, bdd diagram, block definition, block definition diagram

SYSML_IBD

ibd, ibd diagram, internal block, internal block diagram

SYSML_PACKAGE

package, package diagram

SYSML_PARAMETRIC

parametric, parametric diagram

SYSML_REQUIREMENTS

requirement, requirements, requirement diagram, requirements diagram

SYSML_SEQUENCE

sequence, sequence diagram

SYSML_STATE_MACHINE

state machine, state machine diagram

SYSML_USE_CASE

use case, use case diagram

TREE

tree, tree diagram

UML_CLASS

class, class diagram

List of Available Qualifiers

The table below outlines of all the search qualifiers supported by the Innoslate search system.

Search Qualifier

Example Search

Returns

id:value

Id:1

Entities where the id is equal to specified value.

attributeid:”attribute id=value”

Attributeid:”1=1″

Entities where the specified attribute value equals the searched value.

class:”attribute name=value”

Action:”Percent Complete=45″

Entities where the specified attribute value equals the searched value. See Attribute Search above for more details.

class:name

class:Action

Entities of the specified schema-based class.

diagram:diagram type

diagram:LML_ACTION

Entities that have that specific diagram enum. See Diagram Search above for more details.

diagram:diagram name

diagram:”Action Diagram”

Entities which have that specific diagram name. See Diagram Search above for more details.

relationshipid:relation Id

relationshipid:1

Entities that contain the relationship type.

relationship:relation name

relationship:”decomposed by”

Entities that contain the relationship type.

order:type

order:number

Orders the results by either name, number, or modified in ascending order. Including a minus after the type (ex. order:number-) will sort descending.

is:crossproject

is:crossproject

Entities with cross project relationships.

is:diagram

is:diagram

Entities that have a generated diagram within Innoslate.

is:leaf

is:leaf

Entities with no children (no target relationships on decomposed by).

is:orphan

is:orphan

Entities with no target relationships to any other entity.

is:root

is:root

Entities with no parents (no target relationships on decomposes).

label:name

label:Activity

Entities with the specified label applied.

is:top

is:top

Entities which are the top of an overall hierarchy (documents, root diagrams, etc.).

number:number

number:5.1

Entities with the specified number.

globalid:global Id

globalid:I_1E3MYNY9MGHV_9WCAZFAFXJW6C  

Entities which have the supplied global id.

⚠️ Databases may vary on searches based on stop words. Please see these differences here.

To continue learning about Database View, Click Here.

(Next Article: Database View Versions)