> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/using-search-in-the-designer.md).

# Using Search in the Designer

The LogicNets Designer includes an advanced search function that improves efficiency in working on logicnets and projects. This function allows content modelers to navigate directly to and update data items in specific elements in logicnets and across projects. It is especially useful in large logicnets projects with multiple logicnets and a highly structured project-tree.

The search function, located at the bottom of the Designer screen, is text based and can be applied to different elements in LogicNets projects. Through configuration of the search parameters is it possible to set the scope and elements to search for.

The search function helps Designer users to find and select a logicnet in the project tree or to find a particular resource (css, topic, document, layout template). It also allows you to search the data model to find which elements refer to a particular data object.

## Search Panel

Users can open the search panel with keyboard short-cut keys **CTRL-F**, **F3**, **SHIFT+F3**, and they can minimize/collapse the panel by clicking on the cross at the top-right of the panel.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6df754518eda5d6297c4ff581eb25a13180213f9%2F7e7c6629-dd92-488d-9204-8a28190130b3.png?alt=media)

## Supported Elements

The search function allows Designer users to search for the following elements across logicnets and projects. The system searches across the following:

* Project settings with text values matching the search string.
* Project items in the project tree with names that match the search string:
  * Logicnets
  * Images, media, documents, tables, topics, .js, or .css files
  * Folders
* Nodes with IDs and/or labels matching the search string
* Parameters from logicnets, nodes, and parts with text values matching the search string. Note: this also includes rules and database queries.
* Text in .js files, .css files, topics, matching the search string

## Start/Stop Searching

Users type the search string in the field located in the top section of the search panel and then clicking the search button next to text input. Next to the search button the user can also narrow the search to the current view, the current project, or the workspace. Users can also specify that the search function match the search case.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-63d94b3daf3137a77d71eee4df71b0b64ee47d39%2Fc17f983e-7ff1-4272-9fde-45adc6734741.png?alt=media)

While performing the search the system will display a progress/wait screen. During this time it is possible to cancel the search.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e0dcafabdca449c74805fa13a4c92ba95094e05e%2F1ab662a1-25e2-4006-a66d-86b95885e015.png?alt=media)

The search function makes use of indexing to optimize performance, but bigger searches may require slightly more time. For example, searching across a workspace will take longer than searching in a project. Search speed may also be affected by server specifications and network connection speeds.

## Search Results

Once a search is completed the system will display the results in the search panel that can be sorted and filtered. It groups results together based on location.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-13eafee1f9074d3f082f84e9181556f14c341050%2F30be82cd-7783-46d6-9f24-ab0d0b716d6e.png?alt=media)

## Matches Returned

Each set of search results starts with a summary that lists the the applied search parameters and the number of matches found.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7724a33313c9ea7254aea38df92355bebe8bac75%2F052eead0-78e9-4e0f-9a3d-dafdcadb3ef8.png?alt=media)

## Displayed Results

The system displays the path to the searched-for element.

The results display grid also displays the match itself, with the matching string in bold. When the matching string exceeds 150 characters the system truncates the text and adds ... to the end.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-44ca8129ec89f88cc34e6a9a313cd5061ee58977%2Fcee12516-17a6-47d9-b1ea-9db2551aaa4d.png?alt=media)

In addition to the path and match, the system displays the match type: parameter, image, document, topic, .js file, .css file, table, folder, or text.

Designers users can collapse or expand each group of search results by clicking the ‘+’ or ‘–‘ buttons on the search results group.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-5ebf6ddc0186565b2d14453eacba306c692dc3e1%2F7fa2ccea-ad7f-4ec2-a7eb-8b4026763432.png?alt=media)

* In collapsed state, the grid shows the summary listing the applied search parameters and the number of hits.
* In expanded state, the grid displays found matches.

The system retains previous search results and displays them in the search panel so they are available to the Designer user, even if the user minimizes the search panel. The user can clear these results by clicking the *Clear results* button. Search results are session specific, however, and the system clears them once the session is closed. The system also clears the search history if the user performs a new search without clicking the checkbox next to *Keep history*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-112411abfeb0d42bb3fc1321af557d6f5b928fe5%2Fe3000696-f390-44c6-98c5-f6b7c718723e.png?alt=media)

## Navigating Search Results

Designer users can navigate through their search results using a mouse and clicking items in the grid. They can also use **F3** and **SHIFT+ F3** shortcut keys.

* F3 selects the next search result and SHIFT+ F3 selects the previous result. They will automatically jump the user to the previous or next set of search results when the user is at the end or beginning of the current set of search results.
* When the search panel is closed F3, or SHIFT+ F3 automatically open the search panel again.

When a user clicks on a search result the system takes them to the location of that result. If the result is in a logicnet, for example, the system will open the logicnet and node where the result is located. The system will also open the appropriate editor. Note: When a user navigates to a search result the system will not automatically save any unsaved changes.

If a user selects a previous search result, it is possible that the element no longer exists or that the searched-for text has been changed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/getting-started/the-logicnets-designer/using-search-in-the-designer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.