Search result
This table shows the search areas in the Name list and the information in each search area:
| Search area | Details |
|---|---|
| Index |
This area shows the element icons and the chronological index order of the element. You cannot search data in this column. Example of icons include a repeating element, a UVJ function, or a parameter. |
| Name | This area shows the element names in a mapping. This name does not need to match the search string. This name can be a parent element in the element’s path that matches the search string. |
| Type | This area shows the type of the element, for example, Doc Input or Doc Output. |
| Path | This area shows the path of the element. An element in this path matches the search string. |
| Description | This area is the description of the element. Multiline descriptions are shown in tool tips. |
To find an element in the mapping editor, double-click an item in the table. You can use the mapping editor to expand the view of parent nodes, scroll to the element, and select the element.
Data for input and output document elements and attributes are read into memory only when they are used. Document elements and attributes in use means that they are connected or expanded in the current editing session. Also called lazy loading, this method is used to avoid too much memory usage, for example, when you store data for a complete BOD schema in memory.
When searching for input or output document elements, search runs on both the memory and schema including all unexpanded elements.
These are the indications and details for search match on elements and attributes:
-
In memory, search matches are indicated by the icons as used in the document tree.
-
In the schema, search matches are indicated by a document icon. The same icon is used for schemas in the Mapping Explorer view.
-
In the schema, search matches are not shown if they are in use.
When you pause on the field headers, tool tips are displayed with brief details on how to run search.
When you pause on an item in the table, more information on the item such as description or data type and length are shown in a tool tip.
When you search on schemas, all schemas known for a mapping are searched including custom schemas, if any. If there are matches in such schemas, the returned paths are relative to the root elements of that schema and not relative to a root element of the input or output schema. In this case, the path is regarded only on the schema where the element is defined. If you double-click the result row, search does not locate the element in the mapping editor.