:

    Benutzerdefinierte Knoten

      2 minute read  

    User-defined nodes can be included in the search index. It must be ensured that the nodes are placed correctly in the tree and a corresponding foreign key has been defined for the search to work.

    Positioning: The node must be placed within the tree structure Inventory below the company level.

    Nodes with Tables

    For the table, a foreign key must be selected in the Manage Tables dialog.

    Nodes with Views

    There are several options for defining and determining the foreign key for the configuration of views, which are used depending on the existing data structure and specific requirements.

    • If a primary table is defined, the foreign key from this table is used. (To use input masks with a view, a primary table must be specified.)
    • If an alternative foreign key has been set for the node in the Manage Objects dialog, this key is used. An alternative foreign key always has priority and is used instead of the foreign key from the primary table.
    • If no foreign key can be determined directly, the closest parent object in the Data category is determined and its primary key is retrieved. If the search object has a column with the same name as the primary key field of the parent object, this column is used as the foreign key.

    Case Study

    A view with the primary table tHosts was created, which returns all systems of type Windows System. The node with the systems is displayed below the company level in the tree. The search index should be created for this view. The foreign key is generated according to the rules above and returns the DomainID of the tHosts table as the foreign key, as tHosts was selected as the primary table. However, the correct foreign key would be the AccountID of the table tDomains.

    Since the foreign key does not match the primary key of the superior object, either no results or incorrect results may be displayed.

    Solution:

    To resolve this, the alternative foreign key for this node can be set to the AccountID in the Manage Objects dialog. This ensures the resolution of the node, and the indexed object appears in the search results.